LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9457: Intense PC Phoenix SecureCore UEFI firmware does not perform capsule signature validation before upgrading...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a firmware trust failure in Intense PC Phoenix SecureCore UEFI: the system may accept firmware updates without validating a capsule signature. An attacker who already has administrator privileges could install modified BIOS firmware, creating persistence below the operating system. The source bundle does not provide affected version ranges, a patch status, or active exploitation evidence. Exposure is most likely on legacy CompuLab Intense PC or MintBox 2 systems using the Phoenix SecureCore UEFI firmware described by the CVE. The bundle lists affected vendor, product, versions, and CPEs as unavailable, so asset confirmation must come from hardware inventory and vendor records. Prioritize discovery and lifecycle decisions rather than emergency patching unless affected systems are confirmed. The business risk is durable compromise of specialized endpoints, but the evidence does not show internet-scale exploitation or a named fixed release in the supplied sources. Mitigation focus: Inventory CompuLab Intense PC and MintBox 2 devices in production.; Check vendor guidance for fixed firmware, replacement, or compensating controls.; Restrict local administrator access on potentially affected systems..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9457 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.