# CVE-2017-20283: Memory corruption in MQX

> A crafted UDP packet can overflow a buffer in NXP MQX RTOS, leading to memory corruption or denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-vq76-7hqc-pgvj

## What is CVE-2017-20283?

CVE-2017-20283 is a medium-severity memory corruption vulnerability in NXP MQX, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NXP MQX Classic before 5.0 contains an out-of-bounds write vulnerability in the RTCS UDP recvfrom() implementation. Improper enforcement of the application-supplied receive buffer length may allow a crafted UDP packet to overflow the destination buffer, resulting in memory corruption, or denial of service.

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

## Which versions are affected by CVE-2017-20283?


## How do I fix CVE-2017-20283?

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

## Is CVE-2017-20283 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20283 and fix it if it is affected.

What it is: CVE-2017-20283 is a medium-severity memory corruption vulnerability in NXP MQX, published on 8 Oct 2026. 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-2017-20283 in the wild and no public exploit code.

Affected product: NXP MQX. 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-2017-20283/ (Markdown: https://insights.sbomify.com/CVE-2017-20283/index.md)
```

## Sources

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

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