Cyber Resilience

CVE-2025-59403

Flocksafety Flock Safety 6.35.31

Public PoC
Published
02 October 2025
Modified
24 November 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.010 60th percentile
Risk Priority 77 floored blend · peak EPSS

Summary

CVE-2025-59403 is a critical-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Flocksafety Flock Safety. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-59403 is a critical vulnerability in the Flock Safety Android Collins application (package name com.flocksafety.android.collins), specifically version 6.35.31 for Android. This application manages camera feeds on Falcon, Sparrow, and Bravo devices but exposes multiple administrative API endpoints on TCP port 8080 without any authentication. Affected endpoints include, but are not limited to, /reboot, /logs, /crashpack, and /adb/enable. The issue stems from CWE-749 (Exposed Dangerous Method or Function) and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

An unauthenticated attacker with network access to the exposed port can exploit these endpoints remotely. Potential impacts include denial of service through the /reboot endpoint, which forces a device restart; information disclosure via /logs and /crashpack, exposing sensitive logs and crash data; and remote code execution via /adb/enable, which starts Android Debug Bridge (ADB) over TCP without requiring debugging confirmation. This grants an attacker on the same LAN or WLAN shell access to the device.

Advisories detailing the vulnerability are published by GainSec at https://gainsec.com/2025/09/27/fly-by-device-2-the-falcon-sparrow-gated-wireless-rce-camera-feed-dos-information-disclosure-and-more/ and https://gainsec.com/wp-content/uploads/2025/09/Root-from-the-Coop-Device-3_-Root-Shell-on-Flock-Safetys-Bravo-Compute-Box-GainSec.pdf. Additional context on affected Flock Safety products, such as license plate readers, is available at https://www.flocksafety.com/products and https://www.flocksafety.com/products/license-plate-readers. No specific patch or mitigation details are provided in the CVE description.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59406Same product: Flocksafety Flock Safety
CVE-2025-59405Same product: Flocksafety Flock Safety
CVE-2025-59407Same product: Flocksafety Flock Safety
CVE-2023-40150Shared CWE-749
CVE-2023-42032Shared CWE-749
CVE-2023-39505Shared CWE-749
CVE-2023-49074Shared CWE-749
CVE-2023-50422Shared CWE-749
CVE-2024-29880Shared CWE-749
CVE-2026-5173Shared CWE-749

Affected Assets

flocksafety
flock safety
6.35.31

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.

Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.

Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.

PR.PS-06 mostly match
prevents

Secure SDLC practices stop developers from exposing dangerous functions in the first place.

ID.RA-01 partial match
prevents

Vulnerability identification processes will surface exposed dangerous methods during assessment.

PR.IR-01 partial match
prevents

Logical access controls at the network/environment layer can limit reachability of exposed functions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.

degrades

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

prevents

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

prevents

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

prevents

Application security requirements can mandate that dangerous methods are not exposed in interfaces.

prevents

Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Ubuntu 22.04 (3 rules)
  • V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
  • V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
  • V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
  • V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749

References