Memory corruption via oversized struct format
Published Nov 29, 2024 · Updated Dec 4, 2024
Integer overflow in NodeMCU Firmware before 3.0.0-release_20240225 allows attackers to corrupt stack memory through crafted Lua struct format strings. The getnum function in app/modules/struct.c accumulates decimal length digits in a signed integer without a bound check, allowing the value to wrap before struct.pack uses it. Reachability requires execution of attacker-controlled Lua, and the public report demonstrates stack memory corruption rather than code execution.
Summary
What happened
Integer overflow in NodeMCU Firmware before 3.0.0-release_20240225 allows attackers to corrupt stack memory through crafted Lua struct format strings. The getnum function in app/modules/struct.c accumulates decimal length digits in a signed integer without a bound check, allowing the value to wrap before struct.pack uses it. Reachability requires execution of attacker-controlled Lua, and the public report demonstrates stack memory corruption rather than code execution.
The record
- CVE
- CVE-2024-36671
- Published
- Nov 29, 2024
- Updated
- Dec 4, 2024
- Vendor
- NodeMCU
- Product
- NodeMCU Firmware
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2024CVE publishedPublication date reported by the CVE source.
- Dec 4, 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 <3.0.0-release_20240225
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
- Oversized struct.pack format proof of conceptproof of concept · unverified
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