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

> A buffer overflow in the Air Force Sensor Data Management System allows attackers to execute arbitrary code via a malicious NITF file.

- **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:** No
- **Published:** 25 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6m48-4c69-4g6c

## What is CVE-2020-13995?

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

### Official description

U.S. Air Force Sensor Data Management System extract75 has a buffer overflow that leads to code execution. An overflow in a global variable (sBuffer) leads to a Write-What-Where outcome. Writing beyond sBuffer will clobber most global variables until reaching a pointer such as DES_info or image_info. By controlling that pointer, one achieves an arbitrary write when its fields are assigned. The data written is from a potentially untrusted NITF file in the form of an integer. The attacker can gain control of the instruction pointer.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Airforce Nitf Extract Utility.

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

No fix has been published for CVE-2020-13995 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-13995 being exploited?

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

Public exploit code:

- https://github.com/dbrumley/extract75-cve-2020-13995 (github_poc): https://github.com/dbrumley/extract75-cve-2020-13995

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13995 is a critical memory corruption vulnerability in n/a, published on 25 Sep 2020. 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-2020-13995 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-13995/ (Markdown: https://insights.sbomify.com/CVE-2020-13995/index.md)
```

## Sources

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

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