CVE-2017-9457 json
Intense PC Phoenix SecureCore UEFI firmware does not perform capsule signature validation before upgrading the system firmware.
published 2017-07-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18390
- cvss
- 6.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
Intense PC Phoenix SecureCore UEFI firmware does not perform capsule signature validation before upgrading the system firmware. The absence of signature validation allows an attacker with administrator privileges to flash a modified UEFI BIOS.
Exploit prediction
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.7 | CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
seclists.org
/fulldisclosure/2017/Jul/56
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/143481/Compulab-Intense-PC-MintBox-2-Signature-Verification.html
third-party-advisory, vdb-entry
-
watchmysys.com
/blog/2017/07/cve-2017-9457-compulab-intense-pc-lacks-firmware-validation/
third-party-advisory
Sources
- CVE List CVE-2017-9457
- NVD CVE-2017-9457
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.