CVE-2025-59403
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Flock Safety Android Collins application (version 6.35.31) used for camera feeds on Falcon, Sparrow, and Bravo devices exposes unauthenticated administrative API endpoints on port 8080. Attackers can access /reboot for denial of service, /logs for information disclosure, and /adb/enable which enables adb over TCP without debugging confirmation, providing remote code execution and shell access to anyone on the local network.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.35.31CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Flock Safety app versionOn the Android device, navigate to Settings > Apps > Flock Safety, or use ADB: `adb shell dumpsys package com.flocksafety.collins | grep versionName`Affected if Version displayed is exactly 6.35.31
-
Verify port 8080 is listeningFrom the device, run `adb shell netstat -tulpn | grep 8080`. Alternatively, scan the device from the network: `nmap -p 8080 <device-ip>`Affected if Port 8080 is open and bound to a service
-
Test /reboot endpoint accessibilitySend an unauthenticated HTTP request to the endpoint: `curl -v http://<device-ip>:8080/reboot`Affected if Request returns a response without HTTP 401 or 403 authentication error
-
Test /logs endpoint accessibilitySend an unauthenticated HTTP request: `curl -v http://<device-ip>:8080/logs`Affected if Request returns log data or directory listing without requiring authentication
-
Test /adb/enable endpoint accessibilitySend an unauthenticated HTTP request: `curl -v http://<device-ip>:8080/adb/enable`Affected if Request returns success response enabling ADB over TCP without requiring debug confirmation
Your environment is affected if Flock Safety Collins app version 6.35.31 is installed AND port 8080 is exposed on the network with any of these unauthenticated endpoints responding successfully.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication on all API endpoints, restrict network access to port 8080 via firewall rules or network segmentation, and apply any available vendor patches.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59403 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59403 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data