Engine crash via static-block semicolon parsing
Published Apr 26, 2024 · Updated Aug 6, 2024
Memory corruption in JerryScript commit ff9ff8f allows local users to crash the engine by executing a crafted JavaScript file. The class-body scanner handles a semicolon after a static block only after identifier validation, leaving inconsistent parser state that reaches a near-null write in vm_loop. Execution of attacker-controlled JavaScript is required; release builds segfault, while debug builds abort on a parser assertion.
Summary
What happened
Memory corruption in JerryScript commit ff9ff8f allows local users to crash the engine by executing a crafted JavaScript file. The class-body scanner handles a semicolon after a static block only after identifier validation, leaving inconsistent parser state that reaches a near-null write in vm_loop. Execution of attacker-controlled JavaScript is required; release builds segfault, while debug builds abort on a parser assertion.
The record
- CVE
- CVE-2024-33258
- Published
- Apr 26, 2024
- Updated
- Aug 6, 2024
- Vendor
- JerryScript Project
- Product
- JerryScript
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=ff9ff8f
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
- Upstream issue 5114 JavaScript crash reproducerproof 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