U-Boot contains a CWE-20: Improper Input Validation vulnerability in Verified boot signature validation that can result in Bypass verified…

published 2018-06-26 8y ago modified 2026-06-17 4mo ago also EUVD-2018-1878

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

U-Boot contains a CWE-20: Improper Input Validation vulnerability in Verified boot signature validation that can result in Bypass verified boot. This attack appear to be exploitable via Specially crafted FIT image and special device memory functionality.

Patch / fix

links 1

lists.denx.de/pipermail/u-boot/2018-June/330454.html advisory

Is CVE-2018-1000205 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-20 Improper Input Validation

References

lists.denx.de /pipermail/u-boot/2018-June/330454.html
mailing-list, patch, vendor-advisory
lists.denx.de /pipermail/u-boot/2018-June/330898.html
mailing-list, mitigation, vendor-advisory

Sources

CVE List CVE-2018-1000205
NVD CVE-2018-1000205

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.