Interpreter crash via typed-array fill write
Published May 27, 2022 · Updated Aug 3, 2024
A segmentation fault in NGINX njs 0.7.2 allows local users to crash the interpreter by running crafted JavaScript. The typed-array setter writes the element and then redundantly calls njs_set_number on its output pointer; the patch removes that second write. The proof of concept requires crafted JavaScript execution, and upstream treats loaded scripts as trusted configuration rather than network-supplied dynamic code.
Summary
What happened
A segmentation fault in NGINX njs 0.7.2 allows local users to crash the interpreter by running crafted JavaScript. The typed-array setter writes the element and then redundantly calls njs_set_number on its output pointer; the patch removes that second write. The proof of concept requires crafted JavaScript execution, and upstream treats loaded scripts as trusted configuration rather than network-supplied dynamic code.
The record
- CVE
- CVE-2022-30503
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2022CVE 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.
Weakness, pattern, technique
Public exploit references
- Typed-array fill crash 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