Process crash via incorrect break jump offset
Published Aug 18, 2022 · Updated Aug 3, 2024
Incorrect jump code generation in NGINX njs 0.7.5 allows attackers to crash the process by executing crafted JavaScript. The njs generator fails to patch a break instruction's JUMP offset when a return appears in an inner try-catch block, so the interpreter follows an invalid offset and reaches a segmentation fault. Exploitation requires executing attacker-controlled JavaScript; NGINX treats imported scripts as trusted configuration and does not dynamically evaluate network input.
Summary
What happened
Incorrect jump code generation in NGINX njs 0.7.5 allows attackers to crash the process by executing crafted JavaScript. The njs generator fails to patch a break instruction's JUMP offset when a return appears in an inner try-catch block, so the interpreter follows an invalid offset and reaches a segmentation fault. Exploitation requires executing attacker-controlled JavaScript; NGINX treats imported scripts as trusted configuration and does not dynamically evaluate network input.
The record
- CVE
- CVE-2022-35173
- Published
- Aug 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-754, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 18, 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.
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
- GitHub issue 553 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