{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59403 exists.","fix":"No fix has been published for CVE-2025-59403 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59403 is a critical missing authorization 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-59403 and fix it if it is affected.\n\nWhat it is: CVE-2025-59403 is a critical missing authorization 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-59403 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-59403/ (Markdown: https://insights.sbomify.com/CVE-2025-59403/index.md)","id":"CVE-2025-59403","markdown":"https://insights.sbomify.com/CVE-2025-59403/index.md","name":"CVE-2025-59403","record":{"aliases":["GHSA-4q23-4xwf-899h"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Flock Safety Android app","requires_auth":"none","summary":"Unauthenticated administrative API endpoints in the Flock Safety Android app allow attackers on the local network to execute code, cause denial of service, or read logs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flock_safety","vendor":"flocksafety"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-749","name":"Exposed Dangerous Method or Function"}],"description":"The Flock Safety Android Collins application (aka com.flocksafety.android.collins) 6.35.31 for Android lacks authentication. It is responsible for the camera feed on Falcon, Sparrow, and Bravo devices, but exposes administrative API endpoints on port 8080 without authentication. Endpoints include but are not limited to: /reboot, /logs, /crashpack, and /adb/enable. This results in multiple impacts including denial of service (DoS) via /reboot, information disclosure via /logs, and remote code execution (RCE) via /adb/enable. The latter specifically results in adb being started over TCP without debugging confirmation, providing an attacker in the LAN/WLAN with shell access.","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":"Missing authorization in n/a","id":"CVE-2025-59403","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2025-59404"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-59402"},"products":["n/a"],"published":"2025-10-02","related":[{"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"},{"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":"total"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["n/a"]},"summary":"Unauthenticated administrative API endpoints in the Flock Safety Android app allow attackers on the local network to execute code, cause denial of service, or read logs.","url":"https://insights.sbomify.com/CVE-2025-59403/"}