# CVE-2019-14239: Security feature bypass in n/a

> Attackers can bypass Flash Access Controls on NXP Kinetis devices to read protected code, exposing intellectual property.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** No
- **Published:** 24 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6399-hf47-6qj8

## What is CVE-2019-14239?

CVE-2019-14239 is a medium-severity vulnerability in n/a, published on 24 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On NXP Kinetis KV1x, Kinetis KV3x, and Kinetis K8x devices, Flash Access Controls (FAC) (a software IP protection method for execute-only access) can be defeated by leveraging a load instruction inside the execute-only region to expose the protected code into a CPU register.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-14239?

It affects 3 products.


Products: Nxp Kinetis K8x Firmware, Nxp Kinetis Kv1x Firmware, Nxp Kinetis Kv3x Firmware.

## How do I fix CVE-2019-14239?

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

## Is CVE-2019-14239 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14237](https://insights.sbomify.com/CVE-2019-14237/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14239 and fix it if it is affected.

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

## Sources

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

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