# CVE-2020-19695: Memory corruption in n/a

> A buffer overflow in the Nginx NJS module allows remote attackers to execute arbitrary code via the njs_object_property parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 4 Apr 2023
- **Updated:** 14 Feb 2025
- **Also known as:** AZL-25994, GHSA-9m49-j2g8-82x8

## What is CVE-2020-19695?

CVE-2020-19695 is a critical memory corruption vulnerability in n/a, published on 4 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow found in Nginx NJS allows a remote attacker to execute arbitrary code via the njs_object_property parameter of the njs/njs_vm.c function.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-19695?

It affects 1 product.


Products: F5 Njs.

## How do I fix CVE-2020-19695?

Apply the vendor's patch.

## Is CVE-2020-19695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-19695 exists.

## Other vulnerabilities in n/a

- [CVE-2020-19692](https://insights.sbomify.com/CVE-2020-19692/): 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)
- [CVE-2021-46463](https://insights.sbomify.com/CVE-2021-46463/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-19695 and fix it if it is affected.

What it is: CVE-2020-19695 is a critical memory corruption vulnerability in n/a, published on 4 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-19695 exists.

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-2020-19695/ (Markdown: https://insights.sbomify.com/CVE-2020-19695/index.md)
```

## Sources

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

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