Skip to content
Fencer Intel
medium 6.0

CVE-2017-7932 json

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,…

published 2017-08-07 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16903

cvss
6.0
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-17-152-02 updated cvss 6.0

NXP i.MX Product Family

  • i.MX .MX 7Solo i.MX 6Dual i.MX 6DualLite i.MX 6DualPlus i.MX 6Quad i.MX 6QuadPlus
    +12 more products
    i.MX 6Solo i.MX 6SoloLite i.MX 6SoloX i.MX 6ULL i.MX 6UltraLit i.MX 7Dual i.MX 28 i.MX 50 i.MX 53 i.MX Vybrid VF3xx i.MX Vybrid VF5xx i.MX Vybrid VF6xx
    affected: mitigation “Because this is a hardware vulnerability, there are no software workarounds available.”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.0 CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
NVD 2.0 4.4 AV:L/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • n/a NXP i.MX Product Family

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.