CVE-2024-29955: Insertion of Sensitive Information into Brocade SANnav Log File
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. This could provide attackers with an additional, less-protected path to acquiring the encryption key.
- Published
- Apr 17, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-532
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · brocade
- 5.0
- 0.5 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| broadcom | brocade sannav | cpe:2.3:a:broadcom:brocade_sannav |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (brocade). Independent of NVD's CPE analysis and usually ahead of it.
Brocade Brocade SANnav
- before v2.3.1 and v2.3.0aaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom brocade sannavbefore 2.3.0a
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-4173SANnav versions exposes Kafka in the wan interface.39Monitor
- CVE-2024-29966hard-coded credentials in the documentation that appear as the appliance root password39Monitor
- CVE-2023-31424Web authentication and authorization bypass39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-29951Apr 17, 2024 · Brocade SANnav has weak encryption in internal SSH ports22Monitor
- ← EarlierCVE-2024-29952Apr 17, 2024 · Clear text storage of sensistive information by manipulating command variables22Monitor
- Later →CVE-2024-29956Apr 17, 2024 · cleartext password in supportsave logs when a user schedules a switch Supportsave from Brocade SANnav26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-299592 days apartBrocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save34Monitor
- CVE-2025-1053303 days apartBrocade SANnav encryption key is logged in the debug logs34Monitor
- CVE-2024-299572 days apartEncryption key is stored in the DR log files30Monitor
- CVE-2024-299582 days apartEncryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node.26Monitor
- CVE-2025-6392449 days apartDaily Data Dump Collector logs database password in cleartext when running docker exec commands (CVE-2025-6392)26Monitor
- CVE-2022-43937218 days apartBrocade SANnav Information Disclosure Vulnerability22Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0308 · Apr 18, 2024(Brocade Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.