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

> An out-of-bounds read in the njs JavaScript engine used by NGINX can lead to crashes or information disclosure.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** AZL-35029, GHSA-88pj-43x4-vj4q

## What is CVE-2020-24347?

CVE-2020-24347 is a medium-severity memory corruption vulnerability in n/a, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_lvlhsh_level_find in njs_lvlhsh.c.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: F5 Njs.

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

Upgrade to a fixed version.

## Is CVE-2020-24347 being exploited?

There is no known exploitation of CVE-2020-24347 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-2020-24347 and fix it if it is affected.

What it is: CVE-2020-24347 is a medium-severity memory corruption vulnerability in n/a, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24347 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-2020-24347/ (Markdown: https://insights.sbomify.com/CVE-2020-24347/index.md)
```

## Sources

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

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