{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-4662 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4662 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4662 is a medium-severity vulnerability in Broadcom Brocade Sannav, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-4662 and fix it if it is affected.\n\nWhat it is: CVE-2025-4662 is a medium-severity vulnerability in Broadcom Brocade Sannav, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-4662 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-2025-4662/ (Markdown: https://insights.sbomify.com/CVE-2025-4662/index.md)","id":"CVE-2025-4662","markdown":"https://insights.sbomify.com/CVE-2025-4662/index.md","name":"CVE-2025-4662","record":{"aliases":["GHSA-5jx5-2f25-63x5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Brocade SANnav","requires_auth":"high_privilege","summary":"Brocade SANnav logs plaintext passphrases in host server audit logs, exposing sensitive credentials to local server administrators.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"brocade","cpe":[{"product":"brocade_sannav","vendor":"broadcom"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"}],"description":"Brocade SANnav before SANnav 2.4.0a logs plaintext passphrases in the Brocade SANnav host server audit logs while executing OpenSSL command using a passphrase from the command line or while providing the passphrase through a temporary file.\n\nThese audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user.","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":"Plaintext security passwords are logged in the audit logs while executing openssl cmd","id":"CVE-2025-4662","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"broadcom:brocade_sannav","products":["broadcom:brocade_sannav"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Denial-of-Service (DoS) after Unusual or Exceptional Conditions vulnerability","id":"CVE-2025-4663"},"packages":[],"prev":{"headline":"Path transversal vulnerability potentially leading to sensitive information disclosure","id":"CVE-2025-4661"},"products":["Brocade SANnav"],"published":"2025-07-10","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":"partial"},"state":"PUBLISHED","updated":"2025-07-11","vendors":["Broadcom"]},"summary":"Brocade SANnav logs plaintext passphrases in host server audit logs, exposing sensitive credentials to local server administrators.","url":"https://insights.sbomify.com/CVE-2025-4662/"}