Device reboot via corrupted Bluetooth transmit buffer
Published May 9, 2024 · Updated Feb 13, 2025
Memory corruption in ESP-IDF 5.1 allows attackers with modified firmware on an ESP32 board to trigger a reboot through Bluetooth traffic. In avdt_ad_write_req, the published reproduction replaces BT_HDR metadata and payload bytes with random values before L2CA_DataWrite processes the buffer. The demonstrated path requires source modification, a local build, and physical flashing; it does not establish remote code execution against unmodified firmware.
Summary
What happened
Memory corruption in ESP-IDF 5.1 allows attackers with modified firmware on an ESP32 board to trigger a reboot through Bluetooth traffic. In avdt_ad_write_req, the published reproduction replaces BT_HDR metadata and payload bytes with random values before L2CA_DataWrite processes the buffer. The demonstrated path requires source modification, a local build, and physical flashing; it does not establish remote code execution against unmodified firmware.
The record
- CVE
- CVE-2024-33454
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- Espressif Systems
- Product
- ESP-IDF
- Classifications
- CWE-120
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1
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
- Bluetooth reboot reproductionproof of concept · demonstrated
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