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
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.
- Published
- Aug 7, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 16th percentile
- CWE
- CWE-295
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nxp | vybrid mvf30nn151cku26 firmware | cpe:2.3:o:nxp:vybrid_mvf30nn151cku26_firmware |
| nxp | vybrid mvf30nn151cku26 | cpe:2.3:h:nxp:vybrid_mvf30nn151cku26 |
| nxp | vybrid mvf30ns151cku26 firmware | cpe:2.3:o:nxp:vybrid_mvf30ns151cku26_firmware |
| nxp | vybrid mvf30ns151cku26 | cpe:2.3:h:nxp:vybrid_mvf30ns151cku26 |
| nxp | vybrid mvf50nn151cmk40 firmware | cpe:2.3:o:nxp:vybrid_mvf50nn151cmk40_firmware |
| nxp | vybrid mvf50nn151cmk40 | cpe:2.3:h:nxp:vybrid_mvf50nn151cmk40 |
| nxp | vybrid mvf50nn151cmk50 firmware | cpe:2.3:o:nxp:vybrid_mvf50nn151cmk50_firmware |
| nxp | vybrid mvf50nn151cmk50 | cpe:2.3:h:nxp:vybrid_mvf50nn151cmk50 |
| nxp | vybrid mvf50ns151cmk40 firmware | cpe:2.3:o:nxp:vybrid_mvf50ns151cmk40_firmware |
| nxp | vybrid mvf50ns151cmk40 | cpe:2.3:h:nxp:vybrid_mvf50ns151cmk40 |
| nxp | vybrid mvf50ns151cmk50 firmware | cpe:2.3:o:nxp:vybrid_mvf50ns151cmk50_firmware |
| nxp | vybrid mvf50ns151cmk50 | cpe:2.3:h:nxp:vybrid_mvf50ns151cmk50 |
and 48 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nxp i.mx 28 firmwareall versions
- nxp i.mx 50 firmwareall versions
- nxp i.mx 53 firmwareall versions
- nxp i.mx 6dual firmwareall versions
- nxp i.mx 6duallite firmwareall versions
- nxp i.mx 6dualplus firmwareall versions
- nxp i.mx 6quad firmwareall versions
- nxp i.mx 6quadplus firmwareall versions
- nxp i.mx 6solo firmwareall versions
- nxp i.mx 6sololite firmwareall versions
- nxp i.mx 6solox firmwareall versions
- nxp i.mx 6ull firmwareall versions
- nxp i.mx 6ultralite firmwareall versions
- nxp i.mx 7dual firmwareall versions
- nxp i.mx 7solo firmwareall versions
- nxp vybrid mvf30nn151cku26 firmwareall versions
- nxp vybrid mvf30ns151cku26 firmwareall versions
- nxp vybrid mvf50nn151cmk40 firmwareall versions
- nxp vybrid mvf50nn151cmk50 firmwareall versions
- nxp vybrid mvf50ns151cmk40 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
n/a NXP i.MX Product Family
- NXP i.MX Product Familyaffected
Same product
nxp: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7936A 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 6Du25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.