Token disclosure via hardcoded AES key and IV
Published Aug 22, 2025 · Updated Aug 26, 2025
Use of a hard-coded key in Reolink Android App 4.54.0.4.20250526 allows attackers to decrypt stored access and web session tokens. The app embeds a fixed AES key and IV for protecting locally stored tokens, so reverse engineering exposes the cryptographic material needed to decrypt every protected value. The public record does not identify how attackers obtain the stored app data; the demonstrated consequence is disclosure of tokens present in the affected app's storage.
Summary
What happened
Use of a hard-coded key in Reolink Android App 4.54.0.4.20250526 allows attackers to decrypt stored access and web session tokens. The app embeds a fixed AES key and IV for protecting locally stored tokens, so reverse engineering exposes the cryptographic material needed to decrypt every protected value. The public record does not identify how attackers obtain the stored app data; the demonstrated consequence is disclosure of tokens present in the affected app's storage.
The record
- CVE
- CVE-2025-55619
- Published
- Aug 22, 2025
- Updated
- Aug 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-321, T1635
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Reolink Android App Uses Hardcoded AES Key and IV for Sensitive Data Decryptionproof 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