{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-29960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-29960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-29960 is a medium-severity vulnerability in Broadcom Brocade Sannav, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-29960 and fix it if it is affected.\n\nWhat it is: CVE-2024-29960 is a medium-severity vulnerability in Broadcom Brocade Sannav, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-29960 in the wild and no public exploit code.\n\nAffected product: Broadcom Brocade Sannav. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-29960/ (Markdown: https://insights.sbomify.com/CVE-2024-29960/index.md)","id":"CVE-2024-29960","markdown":"https://insights.sbomify.com/CVE-2024-29960/index.md","name":"CVE-2024-29960","record":{"aliases":["GHSA-xcp9-jx79-m233"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Brocade SANnav","requires_auth":"high_privilege","summary":"Identical SSH keys in Brocade SANnav OVA images allow attackers to decrypt SSH traffic and compromise communications.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"brocade","cpe":[{"product":"brocade_sannav","vendor":"broadcom"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. Any Brocade SAnnav VM based on the official OVA images is vulnerable to MITM over SSH. An attacker can decrypt and compromise the SSH traffic to the SANnav.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Identical SSH keys utilized inside the OVA image (CVE-2024-29960)","id":"CVE-2024-29960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"broadcom:brocade_sannav","products":["broadcom:brocade_sannav"],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"supply-chain attack risk","id":"CVE-2024-29961"},"packages":[],"prev":{"headline":"Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save","id":"CVE-2024-29959"},"products":["Brocade SANnav"],"published":"2024-04-19","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in Brocade SANnav","id":"CVE-2019-16211","kev_date_added":null,"published":"2020-09-25"},{"cvss_score":9,"headline":"RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.","id":"CVE-2024-3596","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":8.8,"headline":"A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection.","id":"CVE-2019-16212","kev_date_added":null,"published":"2020-09-25"},{"cvss_score":8.8,"headline":"Weak cryptography in Brocade SANnav","id":"CVE-2019-16205","kev_date_added":null,"published":"2019-11-08"},{"cvss_score":8.6,"headline":"Docker implementation in Brocade SANnav is missing Audit Rules.","id":"CVE-2024-2240","kev_date_added":null,"published":"2025-02-14"},{"cvss_score":8.6,"headline":"Brocade SANnav encryption key is logged in the debug logs","id":"CVE-2025-1053","kev_date_added":null,"published":"2025-02-14"},{"cvss_score":8.6,"headline":"Syslog traffic sent in clear-text","id":"CVE-2024-4161","kev_date_added":null,"published":"2024-04-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Brocade"]},"summary":"Identical SSH keys in Brocade SANnav OVA images allow attackers to decrypt SSH traffic and compromise communications.","url":"https://insights.sbomify.com/CVE-2024-29960/"}