{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-58385 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58385 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58385 is a high-severity vulnerability in n/a, published on 26 Sep 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-58385 and fix it if it is affected.\n\nWhat it is: CVE-2025-58385 is a high-severity vulnerability in n/a, published on 26 Sep 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-58385 in the wild and no public exploit code.\n\nAffected product: n/a. 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-58385/ (Markdown: https://insights.sbomify.com/CVE-2025-58385/index.md)","id":"CVE-2025-58385","markdown":"https://insights.sbomify.com/CVE-2025-58385/index.md","name":"CVE-2025-58385","record":{"aliases":["GHSA-vhcj-c9x4-2fgg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DOXENSE WATCHDOC","requires_auth":"none","summary":"Attackers can disclose private user PUK codes for Active Directory users due to hard-coded and predictable data in DOXENSE WATCHDOC.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"watchdoc","vendor":"doxense"}],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"In DOXENSE WATCHDOC before 6.1.0.5094, private user puk codes can be disclosed for Active Directory registered users (there is hard-coded and predictable data).","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":"Hardcoded credentials in n/a","id":"CVE-2025-58385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-58386"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2025-58384"},"products":["n/a"],"published":"2025-09-26","related":[],"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-09-26","vendors":["n/a"]},"summary":"Attackers can disclose private user PUK codes for Active Directory users due to hard-coded and predictable data in DOXENSE WATCHDOC.","url":"https://insights.sbomify.com/CVE-2025-58385/"}