Process crash via null-destination asynchronous return copy
Published Apr 9, 2023 · Updated Feb 12, 2025
Memory corruption in F5 NGINX NJS 0.7.10 allows remote attackers to crash the process via an undisclosed network input. The njs_vmcode_return path calls memcpy during asynchronous return handling and writes through a null destination address, causing a segmentation fault. The public issue omits the trigger script, so the exact input path and deployment preconditions remain undisclosed.
Summary
What happened
Memory corruption in F5 NGINX NJS 0.7.10 allows remote attackers to crash the process via an undisclosed network input. The njs_vmcode_return path calls memcpy during asynchronous return handling and writes through a null destination address, causing a segmentation fault. The public issue omits the trigger script, so the exact input path and deployment preconditions remain undisclosed.
The record
- CVE
- CVE-2023-27729
- Published
- Apr 9, 2023
- Updated
- Feb 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2023CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record 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
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