Process crash via recursive async use-after-free
Published Feb 14, 2022 · Updated Aug 3, 2024
Use-after-free in the async interpreter in NGINX njs 0.7.0 allows context-dependent attackers to crash the executing process. Recursive async calls store promise and await state on the shared function object, so an inner call overwrites state used after its frame is freed. Exploitation requires execution of attacker-controlled JavaScript; njs does not evaluate network-supplied code and treats imported scripts as trusted configuration.
Summary
What happened
Use-after-free in the async interpreter in NGINX njs 0.7.0 allows context-dependent attackers to crash the executing process. Recursive async calls store promise and await state on the shared function object, so an inner call overwrites state used after its frame is freed. Exploitation requires execution of attacker-controlled JavaScript; njs does not evaluate network-supplied code and treats imported scripts as trusted configuration.
The record
- CVE
- CVE-2022-25139
- Published
- Feb 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 14, 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.
Public exploit references
- Recursive async-function 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