Temporary denial of service via unsafe UEFI variable
Published Jan 14, 2025 · Updated Jul 28, 2025
Improper condition handling in Phoenix SecureCore firmware before the listed branch fixes allows local users to cause a temporary service interruption. Phoenix SCT handles a Phoenix-specific UEFI variable without safely rejecting an exceptional value, leading to unsafe memory access. Administrative firmware-variable access is required, and the documented consequence is temporary denial of service rather than data disclosure or code execution.
Summary
What happened
Improper condition handling in Phoenix SecureCore firmware before the listed branch fixes allows local users to cause a temporary service interruption. Phoenix SCT handles a Phoenix-specific UEFI variable without safely rejecting an exceptional value, leading to unsafe memory access. Administrative firmware-variable access is required, and the documented consequence is temporary denial of service rather than data disclosure or code execution.
The record
- CVE
- CVE-2024-29979
- Published
- Jan 14, 2025
- Updated
- Jul 28, 2025
- Vendor
- Phoenix Technologies
- Product
- SecureCore for Intel Ice Lake
- Classifications
- CWE-754, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jul 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.2.0.334
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo