CyberSecBulletin
CVE-2024-0762NVD status: Analyzed

SecureCore™ for Intel Kaby Lake: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2024-0762 is a high-severity buffer copy without checking size of input vulnerability in SecureCore™ for Intel Kaby Lake from Phoenix, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 4.0.1.998 as the first without the flaw, so updating SecureCore™ for Intel Kaby Lake to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.76% chance of exploitation within 30 days, higher than 56% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update SecureCore™ for Intel Kaby Lake to 4.0.1.998 or a later version.
  2. Update SecureCore™ for Intel Coffee Lake to 4.1.0.562 or a later version.
  3. Update SecureCore™ for Intel Ice Lake to 4.2.0.323 or a later version.
  4. Read the advisory on phoenixtech.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
PhoenixSecureCore™ for Intel Kaby Lake4.0.1.1 up to, but not including, 4.0.1.9984.0.1.998
PhoenixSecureCore™ for Intel Coffee Lake4.1.0.1 up to, but not including, 4.1.0.5624.1.0.562
PhoenixSecureCore™ for Intel Ice Lake4.2.0.1 up to, but not including, 4.2.0.3234.2.0.323
PhoenixSecureCore™ for Intel Comet Lake4.2.1.1 up to, but not including, 4.2.1.2874.2.1.287
PhoenixSecureCore™ for Intel Tiger Lake4.3.0.1 up to, but not including, 4.3.0.2364.3.0.236
PhoenixSecureCore™ for Intel Jasper Lake4.3.1.1 up to, but not including, 4.3.1.1844.3.1.184
PhoenixSecureCore™ for Intel Alder Lake4.4.0.1 up to, but not including, 4.4.0.2694.4.0.269
PhoenixSecureCore™ for Intel Raptor Lake4.5.0.1 up to, but not including, 4.5.0.2184.5.0.218
PhoenixSecureCore™ for Intel Meteor Lake4.5.1.1 up to, but not including, 4.5.1.154.5.1.15
Phoenixsecurecore_technology4.0.1.1 up to, but not including, 4.0.1.998; 4.1.0.1 up to, but not including, 4.1.0.562; 4.2.0.1 up to, but not including, 4.2.0.323; 4.2.1.1 up to, but not including, 4.2.1.287; 4.3.0.1 up to, but not including, 4.3.0.236; 4.3.1.1 up to, but not including, 4.3.1.184; 4.4.0.1 up to, but not including, 4.4.0.269; 4.5.0.1 up to, but not including, 4.5.0.218; and 1 more ranges4.0.1.998, 4.1.0.562, 4.2.0.323, 4.2.1.287, 4.3.0.236, 4.3.1.184

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA
CVSS 3.17.8HighNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.