Firmware replacement via CRC32-only integrity check
Published Jan 28, 2022 · Updated Apr 15, 2025
Improper firmware verification in Reolink RLC-410W 3.0.0.136_20121102 allows attackers to install modified firmware via HTTP. The update binary accepts firmware whose authenticity is protected only by a CRC32 check, not a cryptographic signature. Reachability requires either administrator access to the Upgrade API or a man-in-the-middle position during a legitimate update; exploitation permits persistent firmware modification, including backdoor insertion.
Summary
What happened
Improper firmware verification in Reolink RLC-410W 3.0.0.136_20121102 allows attackers to install modified firmware via HTTP. The update binary accepts firmware whose authenticity is protected only by a CRC32 check, not a cryptographic signature. Reachability requires either administrator access to the Upgrade API or a man-in-the-middle position during a legitimate update; exploitation permits persistent firmware modification, including backdoor insertion.
The record
- CVE
- CVE-2022-21134
- Published
- Jan 28, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1601.001
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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
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