{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1053 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1053 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 14 Feb 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-1053 and fix it if it is affected.\n\nWhat it is: CVE-2025-1053 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 14 Feb 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-1053 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-1053/ (Markdown: https://insights.sbomify.com/CVE-2025-1053/index.md)","id":"CVE-2025-1053","markdown":"https://insights.sbomify.com/CVE-2025-1053/index.md","name":"CVE-2025-1053","record":{"aliases":["GHSA-jx64-r67p-6v8c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SAN management software","requires_auth":"none","summary":"An attacker with privileged database access can retrieve encryption keys from debug logs to decrypt stored passwords in Brocade SANnav.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"brocade","cpe":[{"product":"brocade_sannav","vendor":"broadcom"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Under certain error conditions at time of SANnav installation or upgrade, the encryption key can be written into and obtained from a Brocade SANnav supportsave.  An attacker with privileged access to the Brocade SANnav database could use the encryption key to obtain passwords used by Brocade 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":"Brocade SANnav encryption key is logged in the debug logs","id":"CVE-2025-1053","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":"Cross-site scripting in UiCore Elements – Free widgets and templates for Elementor","id":"CVE-2025-1054"},"packages":[],"prev":{"headline":"Mintty Sixel Image Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2025-1052"},"products":["Brocade SANnav"],"published":"2025-02-14","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":"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":"2025-09-09","vendors":["Brocade"]},"summary":"An attacker with privileged database access can retrieve encryption keys from debug logs to decrypt stored passwords in Brocade SANnav.","url":"https://insights.sbomify.com/CVE-2025-1053/"}