Interpreter crash via runtime teardown assertion
Published Apr 26, 2024 · Updated Nov 21, 2024
Reachable assertion in QuickJS on Ubuntu 10.04 allows local users to crash the interpreter with a crafted JavaScript program. The nested-Proxy test reaches a TypeError, leaves the runtime garbage-collection object list nonempty, and triggers the list_empty assertion in JS_FreeRuntime. Execution of attacker-controlled JavaScript is required; the demonstrated result is an abort of the QuickJS process, not a system-wide shutdown.
Summary
What happened
Reachable assertion in QuickJS on Ubuntu 10.04 allows local users to crash the interpreter with a crafted JavaScript program. The nested-Proxy test reaches a TypeError, leaves the runtime garbage-collection object list nonempty, and triggers the list_empty assertion in JS_FreeRuntime. Execution of attacker-controlled JavaScript is required; the demonstrated result is an abort of the QuickJS process, not a system-wide shutdown.
The record
- CVE
- CVE-2024-33263
- Published
- Apr 26, 2024
- Updated
- Nov 21, 2024
- Vendor
- Canonical
- Product
- Ubuntu
- Classifications
- CWE-617, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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=10.04
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.
Public exploit references
- QuickJS issue 277 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