{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59405 exists.","fix":"No fix has been published for CVE-2025-59405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59405 is a high-severity vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59405 and fix it if it is affected.\n\nWhat it is: CVE-2025-59405 is a high-severity vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59405 exists.\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-59405/ (Markdown: https://insights.sbomify.com/CVE-2025-59405/index.md)","id":"CVE-2025-59405","markdown":"https://insights.sbomify.com/CVE-2025-59405/index.md","name":"CVE-2025-59405","record":{"aliases":["GHSA-qh2v-jcx5-rjm9"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Flock Safety Android app","requires_auth":"none","summary":"Attackers can extract a hardcoded DataDog API key from the Flock Safety Android app, potentially compromising monitoring data and bypassing security controls.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flock_safety","vendor":"flocksafety"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Flock Safety Peripheral com.flocksafety.android.peripheral application 7.38.3 for Android (installed on Falcon and Sparrow License Plate Readers and Bravo Edge AI Compute Devices) contains a cleartext DataDog API key within in its codebase. Because application binaries can be trivially decompiled or inspected, attackers can recover the OAuth secret without special privileges. This secret is intended to remain confidential and should never be embedded directly in client-side software.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59406"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-59404"},"products":["n/a"],"published":"2025-10-02","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-59403","kev_date_added":null,"published":"2025-10-02"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59407","kev_date_added":null,"published":"2025-10-02"},{"cvss_score":6.2,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59406","kev_date_added":null,"published":"2025-10-02"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["n/a"]},"summary":"Attackers can extract a hardcoded DataDog API key from the Flock Safety Android app, potentially compromising monitoring data and bypassing security controls.","url":"https://insights.sbomify.com/CVE-2025-59405/"}