Remote code execution via underflowed payload length
Published Jun 5, 2020 · Updated Sep 17, 2024
Buffer overflow in Zephyr RTOS 2.2.0 MQTT parsing allows remote attackers to execute code through a malformed PUBLISH message. The publish_decode function subtracts the parsed variable-header length from a smaller attacker-declared packet length, underflowing the payload length. The MQTT library must be enabled and process attacker-controlled traffic; exploitation can corrupt device memory or execute code in the firmware context.
Summary
What happened
Buffer overflow in Zephyr RTOS 2.2.0 MQTT parsing allows remote attackers to execute code through a malformed PUBLISH message. The publish_decode function subtracts the parsed variable-header length from a smaller attacker-declared packet length, underflowing the payload length. The MQTT library must be enabled and process attacker-controlled traffic; exploitation can corrupt device memory or execute code in the firmware context.
The record
- CVE
- CVE-2020-10071
- Published
- Jun 5, 2020
- Updated
- Sep 17, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120, CWE-129, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 5, 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.2.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