# CVE-2021-46462: Null dereference in n/a

> A segmentation violation in the njs library allows attackers to cause a denial of service via crafted input.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2021-46462, CLEANSTART-2026-ML08252, GHSA-ghww-grw3-m7r6

## What is CVE-2021-46462?

CVE-2021-46462 is a high-severity vulnerability in n/a, published on 14 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

njs through 0.7.1, used in NGINX, was discovered to contain a segmentation violation via njs_object_set_prototype in /src/njs_object.c.

## Which versions are affected by CVE-2021-46462?

It affects 1 product.


Products: F5 Njs.

## How do I fix CVE-2021-46462?

Upgrade to a fixed version.

## Is CVE-2021-46462 being exploited?

There is no known exploitation of CVE-2021-46462 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-19692](https://insights.sbomify.com/CVE-2020-19692/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-19695](https://insights.sbomify.com/CVE-2020-19695/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-43286](https://insights.sbomify.com/CVE-2022-43286/): Use after free in n/a (critical 9.8)
- [CVE-2022-29379](https://insights.sbomify.com/CVE-2022-29379/): Denial of service in n/a (critical 9.8)
- [CVE-2022-27007](https://insights.sbomify.com/CVE-2022-27007/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46462 and fix it if it is affected.

What it is: CVE-2021-46462 is a high-severity vulnerability in n/a, published on 14 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46462 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-46462/ (Markdown: https://insights.sbomify.com/CVE-2021-46462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-46462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-46462
- OSV: https://osv.dev/vulnerability/CVE-2021-46462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-46462/
Summaries are generated and may contain mistakes; the official description above is the record.