Security readout for executives and security teams
Plain-English summary
CVE-2020-24349 is a reported memory-safety flaw in njs, a JavaScript engine used with NGINX. The issue could allow control-flow hijacking in the affected component, but the vendor reportedly considered the NGINX use case low practical risk because no remote attack surface was identified.
Executive priority
Treat this as a targeted hygiene item, not an emergency, unless your environment exposes custom njs logic to untrusted input. The main task is inventory and vendor-guidance validation.
Technical view
The CVE describes control-flow hijack in njs_value_property within njs_value.c affecting njs through 0.4.3. The reference to CWE-416 indicates a use-after-free class issue. Public metadata does not provide CVSS scoring, detailed affected downstream products, or confirmed exploitability beyond the reported code-level flaw.
Likely exposure
Exposure is most likely limited to environments that deploy njs through 0.4.3 and execute relevant njs functionality. The provided sources do not identify broad remote exposure, and the vendor note says the NGINX use case has no remote attack surface.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation. The issue is described as control-flow hijack, but practical exploitation conditions are not established in the provided evidence.
Researcher notes
The public record is sparse: no CVSS, no concrete affected CPEs, and no confirmed exploit activity. Focus analysis on njs through 0.4.3, the njs_value_property code path, and whether deployment context creates attacker-controlled reachability.
Mitigation direction
- Inventory NGINX deployments that include or load njs.
- Identify any njs versions through 0.4.3.
- Check NGINX njs and vendor guidance for fixed versions or compensating controls.
- Prioritize remediation where untrusted users can influence njs execution paths.
Validation and detection
- Confirm whether njs is installed, loaded, or packaged with the deployment.
- Record the deployed njs version for each affected system.
- Review application configuration for njs usage in request handling.
- Check vendor advisories for product-specific impact statements.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-24349 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://cwe.mitre.org/data/definitions/416.htmlCVE reference · x_refsource_MISC
- https://github.com/nginx/njs/issues/324CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20200918-0001/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.