# CVE-2021-44479: Information disclosure in n/a

> An attacker with physical access can read protected flash memory from NXP Kinetis K82 devices by exploiting a buffer over-read in USB ISP mode.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:L/A:L/C:H/I:N/PR:L/S:U/UI:N`)
- **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:** No
- **Published:** 1 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vvcf-vw9f-7qr5

## What is CVE-2021-44479?

CVE-2021-44479 is a medium-severity vulnerability in n/a, published on 1 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NXP Kinetis K82 devices have a buffer over-read via a crafted wlength value in a GET Status-Other request during use of USB In-System Programming (ISP) mode. This discloses protected flash memory.

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

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

It affects 1 product.


Products: Nxp Kinetis K82 Firmware.

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

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

## Is CVE-2021-44479 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44479 is a medium-severity vulnerability in n/a, published on 1 Dec 2021. 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-2021-44479 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-44479/ (Markdown: https://insights.sbomify.com/CVE-2021-44479/index.md)
```

## Sources

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

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