CVE-2024-12533

Temporary service interruption via unsafe UEFI variable handling

Published May 13, 2025 · Updated Jul 28, 2025

Improper condition handling in Phoenix SecureCore Technology 4 allows local users to cause temporary denial of service via a UEFI variable. Firmware handling of crafted UEFI variable data fails to check unusual or exceptional conditions before memory access, producing unsafe memory access. Low-privileged local access is required, and the documented consequence is a temporary service interruption rather than data disclosure or code execution.

CVSS severity3.3
Low
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper condition handling in Phoenix SecureCore Technology 4 allows local users to cause temporary denial of service via a UEFI variable. Firmware handling of crafted UEFI variable data fails to check unusual or exceptional conditions before memory access, producing unsafe memory access. Low-privileged local access is required, and the documented consequence is a temporary service interruption rather than data disclosure or code execution.

The record

CVE
CVE-2024-12533
Published
May 13, 2025
Updated
Jul 28, 2025
Vendor
Phoenix Technologies
Product
SecureCore Technology 4
Classifications
CWE-754, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 13, 2025CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=4.0.1.0 <4.0.1.1018
  2. Affected versionversion=4.1.0.1 <4.1.0.573
  3. Affected versionversion=4.2.0.1 <4.2.0.338
  4. Affected versionversion=4.2.1.1 <4.2.1.300
  5. Affected versionversion=4.3.0.1 <4.3.0.244
  6. Affected versionversion=4.3.1.1 <4.3.1.187
  7. Affected versionversion=4.4.0.1 <4.4.0.299
  8. Affected versionversion=4.5.0.1 <4.5.0.231
  9. Affected versionversion=4.5.1.1 <4.5.1.103
  10. Affected versionversion=4.5.5.1 <4.5.5.36
  11. Affected versionversion=4.6.0.1 <4.6.0.67

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Phoenix Technologies · SecureCore Technology 4version=4.0.1.0 <4.0.1.1018; version=4.1.0.1 <4.1.0.573; version=4.2.0.1 <4.2.0.338; version=4.2.1.1 <4.2.1.300; version=4.3.0.1 <4.3.0.244; version=4.3.1.1 <4.3.1.187; version=4.4.0.1 <4.4.0.299; version=4.5.0.1 <4.5.0.231; version=4.5.1.1 <4.5.1.103; version=4.5.5.1 <4.5.5.36; version=4.6.0.1 <4.6.0.67

Published CVSS scores

3.3Phoenix Technologies, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-754Improper Check for Unusual or Exceptional Conditions
T1499.004Application or System Exploitation

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