{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-12679 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12679 is a high-severity vulnerability in Brocade SANnav, published on 2 Feb 2026. 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-12679 and fix it if it is affected.\n\nWhat it is: CVE-2025-12679 is a high-severity vulnerability in Brocade SANnav, published on 2 Feb 2026. 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-12679 in the wild and no public exploit code.\n\nAffected product: 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-12679/ (Markdown: https://insights.sbomify.com/CVE-2025-12679/index.md)","id":"CVE-2025-12679","markdown":"https://insights.sbomify.com/CVE-2025-12679/index.md","name":"CVE-2025-12679","record":{"aliases":["GHSA-33j4-gghf-cv63"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Brocade SANnav","requires_auth":"high_privilege","summary":"Authenticated privileged users can view plaintext PBE keys in audit logs during specific migration scenarios, exposing sensitive encryption material.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"brocade","cpe":[{"product":"sannav","vendor":"broadcom"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"A vulnerability in Brocade SANnav before 2.4.0b prints the \nPassword-Based Encryption (PBE) key in plaintext in the system audit log\n file. The vulnerability could allow a remote authenticated attacker \nwith access to the audit logs to access the pbe key.\n\nNote: The vulnerability is only triggered during a migration and not \nin a new installation. The system audit logs are accessible only to a \nprivileged user on the server.\n\nThese audit logs are the local server VM’s audit logs and are not \ncontrolled by SANnav. These logs are only visible to the server admin of\n the host server and are not visible to the SANnav admin or any SANnav \nuser.","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":"Plain text pbe key visible in audit log during Brocade SANnav migration from 2.4.0a to 3.0.0","id":"CVE-2025-12679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Brocade SANnav DataBase plaintext password is logged in failover logs (CVE-2025-12680)","id":"CVE-2025-12680"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-12678"},"products":["SANnav"],"published":"2026-02-02","related":[{"cvss_score":9.8,"headline":"The c_rehash script allows command injection","id":"CVE-2022-2068","kev_date_added":null,"published":"2022-06-21"},{"cvss_score":9.8,"headline":"SQL injection in Brocade SANNav","id":"CVE-2022-28163","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":9.8,"headline":"Server-side request forgery in Brocade SANnav","id":"CVE-2020-15377","kev_date_added":null,"published":"2021-06-09"},{"cvss_score":8.8,"headline":"Missing authorization in Brocade SANNav","id":"CVE-2022-28165","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":8.5,"headline":"Plaintext Switch admin login password is seen in Brocade SANnav support save","id":"CVE-2025-12772","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":7.5,"headline":"Weak cryptography in Brocade SANnav","id":"CVE-2022-28166","kev_date_added":null,"published":"2022-06-27"},{"cvss_score":7.5,"headline":"Information disclosure in Brocade SANnav","id":"CVE-2022-28168","kev_date_added":null,"published":"2022-06-27"}],"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":"2026-02-04","vendors":["Brocade"]},"summary":"Authenticated privileged users can view plaintext PBE keys in audit logs during specific migration scenarios, exposing sensitive encryption material.","url":"https://insights.sbomify.com/CVE-2025-12679/"}