{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6391 is a high-severity vulnerability in Broadcom Brocade ASCG, published on 17 Jul 2025. 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-2025-6391 and fix it if it is affected.\n\nWhat it is: CVE-2025-6391 is a high-severity vulnerability in Broadcom Brocade ASCG, published on 17 Jul 2025. 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-2025-6391 in the wild and no public exploit code.\n\nAffected product: Broadcom Brocade ASCG. 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-6391/ (Markdown: https://insights.sbomify.com/CVE-2025-6391/index.md)","id":"CVE-2025-6391","markdown":"https://insights.sbomify.com/CVE-2025-6391/index.md","name":"CVE-2025-6391","record":{"aliases":["GHSA-cqgv-gr59-9qf6"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Brocade ASCG","requires_auth":"high_privilege","summary":"Attackers with log access can steal JWTs from Brocade ASCG logs, enabling session hijacking and unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"brocade","cpe":[{"product":"brocade_active_support_connectivity_gateway","vendor":"broadcom"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Brocade ASCG before 3.3.0 logs JSON \nWeb Tokens (JWT) in log files. An attacker with access to the log files \n can withdraw the unencrypted tokens with security implications, such as\n unauthorized access, session hijacking, and information disclosure.","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":"JSON Web Token (JWT) Exposure in Log Files","id":"CVE-2025-6391","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":"Daily Data Dump Collector logs database password in cleartext when running docker exec commands (CVE-2025-6392)","id":"CVE-2025-6392"},"packages":[],"prev":{"headline":"Cleartext storage of sensitive information in Brocade SANnav server audit logs.","id":"CVE-2025-6390"},"products":["Brocade ASCG"],"published":"2025-07-17","related":[{"cvss_score":8.7,"headline":"Missing authorization in Brocade Active Support Connectivity Gateway","id":"CVE-2026-85421","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.7,"headline":"Missing authorization in Brocade Active Support Connectivity Gateway","id":"CVE-2026-85489","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.6,"headline":"A vulnerability has been identified in the data collection service of Brocade ASCG versions before 3.5.0.","id":"CVE-2026-85423","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.6,"headline":"Code injection in Brocade Active Support Connectivity Gateway","id":"CVE-2026-85486","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.6,"headline":"Path traversal in Brocade Active Support Connectivity Gateway","id":"CVE-2026-85487","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.6,"headline":"A vulnerability in the SupportLink API authentication component of Brocade ASCG versions prior to 3.5.0 allows an attacker to bypass authent","id":"CVE-2026-87424","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":8.6,"headline":"Medium Strength Cipher Suites detected on port on ports 9000 and 8036","id":"CVE-2025-7398","kev_date_added":null,"published":"2025-07-17"}],"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-07-18","vendors":["Broadcom"]},"summary":"Attackers with log access can steal JWTs from Brocade ASCG logs, enabling session hijacking and unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-6391/"}