Remote code execution via MQTT length overflow
Published Jun 5, 2020 · Updated Sep 16, 2024
Buffer overflow in Zephyr RTOS 2.2.0 allows remote attackers to corrupt memory or execute code via a crafted MQTT packet. mqtt_read_message_chunk subtracts buffered bytes from an attacker-controlled packet length and fails to detect pointer wraparound before reading transport data beyond the receive buffer. The MQTT client must process the packet through its broker connection; exploitation can crash the device or execute code in the firmware context.
Summary
What happened
Buffer overflow in Zephyr RTOS 2.2.0 allows remote attackers to corrupt memory or execute code via a crafted MQTT packet. mqtt_read_message_chunk subtracts buffered bytes from an attacker-controlled packet length and fails to detect pointer wraparound before reading transport data beyond the receive buffer. The MQTT client must process the packet through its broker connection; exploitation can crash the device or execute code in the firmware context.
The record
- CVE
- CVE-2020-10070
- Published
- Jun 5, 2020
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-190, CWE-120, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 5, 2020CVE 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=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