Development-build crash via miscalculated module path length
Published May 25, 2022 · Updated Aug 3, 2024
Stack-buffer overflow in NGINX njs allows attackers to crash an unreleased development build by importing an overlong module path. The njs_module_path function replaces the required buffer length with the directory length instead of adding it, then copies the full joined path into the undersized stack buffer. Upstream states the defect existed only between unreleased commits, so 0.7.2 through 0.7.4 are unaffected; triggering it requires control of trusted JavaScript loaded at startup.
Summary
What happened
Stack-buffer overflow in NGINX njs allows attackers to crash an unreleased development build by importing an overlong module path. The njs_module_path function replaces the required buffer length with the directory length instead of adding it, then copies the full joined path into the undersized stack buffer. Upstream states the defect existed only between unreleased commits, so 0.7.2 through 0.7.4 are unaffected; triggering it requires control of trusted JavaScript loaded at startup.
The record
- CVE
- CVE-2022-29379
- Published
- May 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 25, 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
No public exploit references are available in this record.
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