dbcve.org
Securecore TechnologyOperating system · Phoenixtech

CVE-2024-0762

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 4.0.1.998 / 4.1.0.562 or later.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Potential buffer overflow in unsafe UEFI variable handling in Phoenix SecureCore™ for select Intel platforms This issue affects: Phoenix SecureCore™ for Intel Kaby Lake: from 4.0.1.1 before 4.0.1.998; Phoenix SecureCore™ for Intel Coffee Lake: from 4.1.0.1 before 4.1.0.562; Phoenix SecureCore™ for Intel Ice Lake: from 4.2.0.1 before 4.2.0.323; Phoenix SecureCore™ for Intel Comet Lake: from 4.2.1.1 before 4.2.1.287; Phoenix SecureCore™ for Intel Tiger Lake: from 4.3.0.1 before 4.3.0.236; Phoenix SecureCore™ for Intel Jasper Lake: from 4.3.1.1 before 4.3.1.184; Phoenix SecureCore™ for Intel Alder Lake: from 4.4.0.1 before 4.4.0.269; Phoenix SecureCore™ for Intel Raptor Lake: from 4.5.0.1 before 4.5.0.218; Phoenix SecureCore™ for Intel Meteor Lake: from 4.5.1.1 before 4.5.1.15.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-120

A fixed-size buffer is filled without checking the length of the incoming data, so it overflows into neighbouring memory. This is the classic overflow attackers use to overwrite return addresses and hijack execution. The fix is strict length checks and safe, bounded string and memory functions.

General guidance for the classic buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Securecore TechnologyOperating system
Affected:>= 4.0.1.1, < 4.0.1.998>= 4.1.0.1, < 4.1.0.562>= 4.2.0.1, < 4.2.0.323>= 4.2.1.1, < 4.2.1.287>= 4.3.0.1, < 4.3.0.236>= 4.3.1.1, < 4.3.1.184>= 4.4.0.1, < 4.4.0.269>= 4.5.0.1, < 4.5.0.218>= 4.5.1.1, < 4.5.1.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.0.1.998 / 4.1.0.562 / 4.2.0.323 or later
Fixed in 4.0.1.9984.1.0.5624.2.0.323
Recommended fix High confidence

Upgrade to the platform-specific fixed version: 4.0.1.998 (Kaby Lake), 4.1.0.562 (Coffee Lake), 4.2.0.323 (Ice Lake), 4.2.1.287 (Comet Lake), 4.3.0.236 (Tiger Lake), 4.3.1.184 (Jasper Lake), 4.4.0.269 (Alder Lake), 4.5.0.218 (Raptor Lake), or 4.5.1.15 (Meteor Lake)

  1. Identify the specific Intel platform (Kaby Lake, Coffee Lake, Ice Lake, Comet Lake, Tiger Lake, Jasper Lake, Alder Lake, Raptor Lake, or Meteor Lake) and current SecureCore firmware version running on the system
  2. Contact the OEM (Original Equipment Manufacturer) or Phoenix Technologies to obtain the appropriate firmware update for your platform
  3. Request and apply the firmware update that upgrades to the fixed version: Kaby Lake to >=4.0.1.998, Coffee Lake to >=4.1.0.562, Ice Lake to >=4.2.0.323, Comet Lake to >=4.2.1.287, Tiger Lake to >=4.3.0.236, Jasper Lake to >=4.3.1.184, Alder Lake to >=4.4.0.269, Raptor Lake to >=4.5.0.218, or Meteor Lake to >=4.5.1.15
  4. After firmware update, verify the SecureCore version has been updated to a fixed release
  5. Confirm the UEFI variable handling no longer exhibits buffer overflow behavior
Caveat Firmware updates carry inherent risks and may require downtime; ensure proper backup and follow OEM update procedures carefully

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0762 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data