# CVE-2017-7936: Memory corruption in NXP i.MX Product Family

> Attackers can execute arbitrary code via SDP in security-enabled NXP i.MX devices due to a stack-based buffer overflow in firmware.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:P/AC:H/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:** 7 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w554-2257-9wrq

## What is CVE-2017-7936?

CVE-2017-7936 is a medium-severity memory corruption vulnerability in NXP i.MX Product Family, published on 7 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow issue was discovered in NXP i.MX 50, i.MX 53, i.MX 6ULL, i.MX 6UltraLite, i.MX 6SoloLite, i.MX 6Solo, i.MX 6DualLite, i.MX 6SoloX, i.MX 6Dual, i.MX 6Quad, i.MX 6DualPlus, i.MX 6QuadPlus, Vybrid VF3xx, Vybrid VF5xx, and Vybrid VF6xx. When the device is configured in security enabled configuration, SDP could be used to download a small section of code to an unprotected region of memory.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-121 (Stack-based Buffer Overflow)

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

It affects 27 products.


Products: Nxp I.mx 50 Firmware, Nxp I.mx 53 Firmware, Nxp I.mx 6dual Firmware, Nxp I.mx 6duallite Firmware, Nxp I.mx 6dualplus Firmware, Nxp I.mx 6quad Firmware, Nxp I.mx 6quadplus Firmware, Nxp I.mx 6solo Firmware, Nxp I.mx 6sololite Firmware, Nxp I.mx 6solox Firmware, Nxp I.mx 6ull Firmware, Nxp I.mx 6ultralite Firmware, Nxp Vybrid Mvf30nn151cku26 Firmware, Nxp Vybrid Mvf30ns151cku26 Firmware, Nxp Vybrid Mvf50nn151cmk40 Firmware, Nxp Vybrid Mvf50nn151cmk50 Firmware, Nxp Vybrid Mvf50ns151cmk40 Firmware, Nxp Vybrid Mvf50ns151cmk50 Firmware, Nxp Vybrid Mvf51nn151cmk50 Firmware, Nxp Vybrid Mvf51ns151cmk50 Firmware and 7 more.

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

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

## Is CVE-2017-7936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7936 is a medium-severity memory corruption vulnerability in NXP i.MX Product Family, published on 7 Aug 2017. 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-2017-7936 in the wild and no public exploit code.

Affected product: NXP i.MX Product Family. 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-7936/ (Markdown: https://insights.sbomify.com/CVE-2017-7936/index.md)
```

## Sources

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

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