Process abort via recursive constructor exhaustion
Published Apr 5, 2022 · Updated Aug 4, 2024
Stack exhaustion in JerryScript before 2021-10-20 allows context-dependent attackers to abort an embedding process with crafted JavaScript. The public test case defines opt() to invoke new opt() recursively, exhausting the native stack until AddressSanitizer terminates the process. GitLab classifies the report as a false positive because the product worked as intended, so no distinct security-boundary violation is established.
Summary
What happened
Stack exhaustion in JerryScript before 2021-10-20 allows context-dependent attackers to abort an embedding process with crafted JavaScript. The public test case defines opt() to invoke new opt() recursively, exhausting the native stack until AddressSanitizer terminates the process. GitLab classifies the report as a false positive because the product worked as intended, so no distinct security-boundary violation is established.
The record
- CVE
- CVE-2021-41752
- Published
- Apr 5, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
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.
Public exploit references
- Recursive constructor test caseproof 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