Credential disclosure via hard-coded P2P key
Published Jan 26, 2021 · Updated Sep 16, 2024
Use of a hard-coded key in Reolink RLC-4XX, RLC-5XX, and RLN-X10 series allows attackers to recover credentials via the local network. The XML-based P2P control protocol encrypts every session with one embedded symmetric key, allowing captured messages to be restored to cleartext. Local-network access and an active P2P exchange are required; recovered device credentials can support later access from outside that network.
Summary
What happened
Use of a hard-coded key in Reolink RLC-4XX, RLC-5XX, and RLN-X10 series allows attackers to recover credentials via the local network. The XML-based P2P control protocol encrypts every session with one embedded symmetric key, allowing captured messages to be restored to cleartext. Local-network access and an active P2P exchange are required; recovered device credentials can support later access from outside that network.
The record
- CVE
- CVE-2020-25173
- Published
- Jan 26, 2021
- Updated
- Sep 16, 2024
- Vendor
- Reolink
- Product
- RLC-5XX series
- Classifications
- CWE-321, CWE-798, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=All versions
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
No public exploit references are available in this record.
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