Security readout for executives and security teams
Plain-English summary
This issue affects njs, the JavaScript engine used with NGINX. The provided sources describe an out-of-bounds array access in njs through 0.7.0. Business urgency depends on whether your NGINX or vendor appliances include njs. No CVSS score, confirmed impact, or active exploitation evidence is provided.
Executive priority
Treat this as a targeted inventory and patch-management item, not an emergency. Escalate if njs is exposed in internet-facing NGINX services or embedded in critical vendor products.
Technical view
CVE-2021-46461 is an out-of-bounds array access in njs_vmcode_typeof within src/njs_vmcode.c, affecting njs through 0.7.0. The source bundle references an upstream issue, an upstream commit, and a NetApp advisory. Impact details and affected downstream product versions are incomplete in the provided evidence.
Likely exposure
Likely exposure is limited to environments running NGINX with njs, or downstream products bundling vulnerable njs versions. NetApp’s advisory indicates downstream vendor relevance, but the bundle does not identify specific affected NetApp product versions here.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public issue and commit references exist, so defenders should assume vulnerability details are discoverable without treating exploitation as confirmed.
Researcher notes
The public record is sparse: no CVSS, CWE, exploit status, or detailed impact is included in the bundle. The strongest technical anchors are the affected version statement, function name, source file, upstream issue, commit, and NetApp advisory.
Mitigation direction
- Inventory NGINX deployments and confirm whether njs is installed or enabled.
- Identify njs versions and prioritize anything through 0.7.0 for remediation review.
- Check NGINX njs upstream guidance for the fixed release or patch commit applicability.
- Review NetApp advisory guidance for any affected NetApp-managed products.
- Apply vendor-supported updates rather than manually backporting unless your vendor supports it.
Validation and detection
- Confirm deployed njs package versions are not through 0.7.0.
- Verify NGINX configurations for use of the njs module.
- Check software composition records for bundled njs in appliances or containers.
- Review vendor advisories for remediation status and product-specific exposure.
- Document systems where njs is absent to reduce false-positive tracking.
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-2021-46461 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://github.com/nginx/njs/issues/450CVE reference · x_refsource_MISC
- https://github.com/nginx/njs/commit/d457c9545e7e71ebb5c0479eb16b9d33175855e2CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20220303-0007/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.
