Process crash via oversized identifier conversion
Published Nov 19, 2021 · Updated Aug 3, 2024
A heap buffer overflow in fxIDToString in OpenSource Moddable 10.5.0 allows local users to corrupt memory via crafted JavaScript. When XS converts a crafted identifier to text, fxIDToString writes 3,349 bytes past a 1,456-byte heap allocation in xsSymbol.c. The user must run the crafted script with xst, and the demonstrated consequence is process abort after heap corruption.
Summary
What happened
A heap buffer overflow in fxIDToString in OpenSource Moddable 10.5.0 allows local users to corrupt memory via crafted JavaScript. When XS converts a crafted identifier to text, fxIDToString writes 3,349 bytes past a 1,456-byte heap allocation in xsSymbol.c. The user must run the crafted script with xst, and the demonstrated consequence is process abort after heap corruption.
The record
- CVE
- CVE-2021-29326
- Published
- Nov 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- fxIDToString heap-buffer-overflow 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