CVE-2022-43937: Brocade SANnav Information Disclosure Vulnerability
First published: Thu Nov 21 2024(Updated: )
Possible information exposure through log file vulnerability where sensitive fields are recorded in the debug-enabled logs when debugging is turned on in Brocade SANnav before 2.3.0 and 2.2.2a
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.2.2a | |
| Broadcom SANnav OVA | <2.3.0<2.2.2a |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-43937?
The severity of CVE-2022-43937 is classified as medium due to potential information exposure.
How do I fix CVE-2022-43937?
To fix CVE-2022-43937, disable debug logging in Brocade SANnav or upgrade to versions 2.3.0 or 2.2.2a or later.
What systems are affected by CVE-2022-43937?
CVE-2022-43937 affects Brocade SANnav versions prior to 2.3.0 and 2.2.2a.
What type of vulnerability is CVE-2022-43937?
CVE-2022-43937 is an information exposure vulnerability related to logging.
Can CVE-2022-43937 lead to data breaches?
Yes, CVE-2022-43937 can potentially lead to data breaches if sensitive information is logged.
- agent/weakness
- agent/title
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/severity
- agent/last-modified-date
- agent/event
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/guess-ai
- vendor/broadcom
- canonical/broadcom sannav ova
- vendor/brocade