Update-download tampering via unvalidated HTTPS certificates
Published May 3, 2024 · Updated Aug 2, 2024
Improper certificate validation in NETGEAR RAX50 firmware before 1.0.15.128 allows man-in-the-middle attackers to alter update downloads. The curl_post update path accepts an HTTPS server certificate without proper validation, allowing substituted content from an attacker on the update route. Router authentication is unnecessary, while root code execution requires chaining the altered download with another vulnerability.
Summary
What happened
Improper certificate validation in NETGEAR RAX50 firmware before 1.0.15.128 allows man-in-the-middle attackers to alter update downloads. The curl_post update path accepts an HTTPS server certificate without proper validation, allowing substituted content from an attacker on the update route. Router authentication is unnecessary, while root code execution requires chaining the altered download with another vulnerability.
The record
- CVE
- CVE-2023-35721
- Published
- May 3, 2024
- Updated
- Aug 2, 2024
- Vendor
- NETGEAR
- Product
- RAX50
- Classifications
- CWE-295, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=0 <1.1.15.128
What conditions does exploitation require?
What is affected?
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.
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