{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59406 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59406 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59406 is a medium-severity vulnerability in n/a, published on 2 Oct 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-59406 and fix it if it is affected.\n\nWhat it is: CVE-2025-59406 is a medium-severity vulnerability in n/a, published on 2 Oct 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-59406 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-59406/ (Markdown: https://insights.sbomify.com/CVE-2025-59406/index.md)","id":"CVE-2025-59406","markdown":"https://insights.sbomify.com/CVE-2025-59406/index.md","name":"CVE-2025-59406","record":{"aliases":["GHSA-34xp-hg92-v4qh"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android license plate reader app","requires_auth":"none","summary":"Attackers can extract hardcoded OAuth secrets from the Android app binary, potentially bypassing authentication and accessing sensitive data.","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":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"The Flock Safety Pisco com.flocksafety.android.pisco application 6.21.11 for Android (installed on Falcon and Sparrow License Plate Readers and Bravo Edge AI Compute Devices) has a cleartext Auth0 client secret in its codebase. Because application binaries can be trivially decompiled or inspected, attackers can recover this 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":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59406","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-59407"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59405"},"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":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-59405","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-02","vendors":["n/a"]},"summary":"Attackers can extract hardcoded OAuth secrets from the Android app binary, potentially bypassing authentication and accessing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-59406/"}