Traffic interception via disabled DTLS peer verification
Published May 11, 2020 · Updated Sep 17, 2024
Improper certificate validation in Zephyr RTOS 2.1.0 and later allows man-in-the-middle attackers to intercept UpdateHub traffic. In lib/updatehub/updatehub.c, the DTLS socket configuration disables peer verification and accepts a server without validating its certificate. Reachability requires an UpdateHub-enabled device and a position on its update path; signed firmware blocks replacement images but not traffic disclosure or interruption.
Summary
What happened
Improper certificate validation in Zephyr RTOS 2.1.0 and later allows man-in-the-middle attackers to intercept UpdateHub traffic. In lib/updatehub/updatehub.c, the DTLS socket configuration disables peer verification and accepts a server without validating its certificate. Reachability requires an UpdateHub-enabled device and a position on its update path; signed firmware blocks replacement images but not traffic disclosure or interruption.
The record
- CVE
- CVE-2020-10059
- Published
- May 11, 2020
- Updated
- Sep 17, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-295, CAPEC-475, CAPEC-459, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=2.1.0 <unspecified
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.
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