Physical credential disclosure via embedded password
Published Jun 27, 2025 · Updated Sep 2, 2025
Hard-coded credentials in Flock Safety LPR firmware through 2.2 allow physically proximate attackers to disclose system secrets. Android APK classes in the firmware embed an API key, a default API key, and a default keystore password as literal values. Physical access and device-debugging knowledge are required, and Flock states that cloud evidence and metadata are unaffected.
Summary
What happened
Hard-coded credentials in Flock Safety LPR firmware through 2.2 allow physically proximate attackers to disclose system secrets. Android APK classes in the firmware embed an API key, a default API key, and a default keystore password as literal values. Physical access and device-debugging knowledge are required, and Flock states that cloud evidence and metadata are unaffected.
The record
- CVE
- CVE-2025-47823
- Published
- Jun 27, 2025
- Updated
- Sep 2, 2025
- Vendor
- Flock Safety
- Product
- Flock LPR
- Classifications
- CWE-259, T1552.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GainSec Falcon/Sparrow firmware credential extractionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo