Buffer overflow via stale Array.slice length
Published Apr 5, 2022 · Updated Aug 4, 2024
Buffer overflow in JerryScript before commit e1ce7dd7271288be8c0c8136eea9107df73a8ce2 allows attackers to trigger memory corruption via Array.slice. The fast-array Array.slice implementation keeps a stale end index when index normalization changes the input length, so element copying reads beyond the valid buffer. Exploitation requires attacker-controlled JavaScript to execute in an embedding application; published records do not establish reliable code execution or exploitation in the wild.
Summary
What happened
Buffer overflow in JerryScript before commit e1ce7dd7271288be8c0c8136eea9107df73a8ce2 allows attackers to trigger memory corruption via Array.slice. The fast-array Array.slice implementation keeps a stale end index when index normalization changes the input length, so element copying reads beyond the valid buffer. Exploitation requires attacker-controlled JavaScript to execute in an embedding application; published records do not establish reliable code execution or exploitation in the wild.
The record
- CVE
- CVE-2021-41751
- Published
- Apr 5, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 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?
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.
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