Runtime crash via restored-frame use-after-free
Published Apr 14, 2022 · Updated Aug 3, 2024
Use-after-free in nginx njs 0.7.2 allows attackers to crash the JavaScript runtime by executing recursive asynchronous code. When await saves a runtime frame, njs_function_frame_save() copies pointers to spare memory that the original frame can free; njs_function_frame_alloc() later clears the freed region after restoring that frame. Triggering the demonstrated abort requires control of JavaScript executed by njs, and the upstream threat model treats such code as trusted configuration rather than dynamically evaluated network input.
Summary
What happened
Use-after-free in nginx njs 0.7.2 allows attackers to crash the JavaScript runtime by executing recursive asynchronous code. When await saves a runtime frame, njs_function_frame_save() copies pointers to spare memory that the original frame can free; njs_function_frame_alloc() later clears the freed region after restoring that frame. Triggering the demonstrated abort requires control of JavaScript executed by njs, and the upstream threat model treats such code as trusted configuration rather than dynamically evaluated network input.
The record
- CVE
- CVE-2022-27007
- Published
- Apr 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 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