Interpreter crash via zero-length integer conversion
Published Sep 17, 2024 · Updated Sep 17, 2024
Heap-based buffer overflow in MicroPython 1.23.0 allows remote attackers to crash the interpreter through a zero-length int.to_bytes call. int_to_bytes accepts a zero output length, allocates an empty buffer, and mpz_as_bytes decrements its pointer before writing a nonzero integer. Exploitation requires attacker-controlled Python code to invoke the conversion; the demonstrated consequence is a segmentation fault.
Summary
What happened
Heap-based buffer overflow in MicroPython 1.23.0 allows remote attackers to crash the interpreter through a zero-length int.to_bytes call. int_to_bytes accepts a zero output length, allocates an empty buffer, and mpz_as_bytes decrements its pointer before writing a nonzero integer. Exploitation requires attacker-controlled Python code to invoke the conversion; the demonstrated consequence is a segmentation fault.
The record
- CVE
- CVE-2024-8948
- Published
- Sep 17, 2024
- Updated
- Sep 17, 2024
- Vendor
- MicroPython
- Product
- MicroPython
- Classifications
- CWE-122, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE 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=1.23.0
What conditions does exploitation require?
What is affected?
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
- Zero-length int.to_bytes crash proof of conceptproof 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