NVD / CVE Program· CNA Phoenix

CVE-2024-0762: Potential buffer overflow when handling UEFI variables

Noroxi assessment

Priority: Monitor (action score 31/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.75% (FIRST EPSS); higher than 54.9% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—Proof of concept No fix recorded

Memory safety

BDU:2024-04743

Published: May 14, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 54th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Phoenix: 7.5; 0.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
intel	celeron 3865u	cpe:2.3:h:intel:celeron_3865u
intel	celeron 3867u	cpe:2.3:h:intel:celeron_3867u
intel	celeron 3965u	cpe:2.3:h:intel:celeron_3965u
intel	celeron 3965y	cpe:2.3:h:intel:celeron_3965y
intel	celeron g3930	cpe:2.3:h:intel:celeron_g3930
intel	celeron g3930t	cpe:2.3:h:intel:celeron_g3930t
intel	celeron g3950	cpe:2.3:h:intel:celeron_g3950
intel	core i3-7020u	cpe:2.3:h:intel:core_i3-7020u
intel	core i3-7100	cpe:2.3:h:intel:core_i3-7100
intel	core i3-7100h	cpe:2.3:h:intel:core_i3-7100h
intel	core i3-7100t	cpe:2.3:h:intel:core_i3-7100t
intel	core i3-7100u	cpe:2.3:h:intel:core_i3-7100u

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

phoenixtech securecore technology4.0.1.1 and later · before 4.0.1.998
phoenixtech securecore technology4.1.0.1 and later · before 4.1.0.562
phoenixtech securecore technology4.2.0.1 and later · before 4.2.0.323
phoenixtech securecore technology4.2.1.1 and later · before 4.2.1.287
phoenixtech securecore technology4.3.0.1 and later · before 4.3.0.236
phoenixtech securecore technology4.3.1.1 and later · before 4.3.1.184
phoenixtech securecore technology4.4.0.1 and later · before 4.4.0.269
phoenixtech securecore technology4.5.0.1 and later · before 4.5.0.218
phoenixtech securecore technology4.5.1.1 and later · before 4.5.1.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Phoenix). Independent of NVD's CPE analysis and usually ahead of it.

Phoenix SecureCore™ for Intel Alder Lake
- 4.4.0.1 and later · before 4.4.0.269affected
Phoenix SecureCore™ for Intel Coffee Lake
- 4.1.0.1 and later · before 4.1.0.562affected
Phoenix SecureCore™ for Intel Comet Lake
- 4.2.1.1 and later · before 4.2.1.287affected
Phoenix SecureCore™ for Intel Ice Lake
- 4.2.0.1 and later · before 4.2.0.323affected
Phoenix SecureCore™ for Intel Jasper Lake
- 4.3.1.1 and later · before 4.3.1.184affected
Phoenix SecureCore™ for Intel Kaby Lake
- 4.0.1.1 and later · before 4.0.1.998affected
Phoenix SecureCore™ for Intel Meteor Lake
- 4.5.1.1 and later · before 4.5.1.15affected
Phoenix SecureCore™ for Intel Raptor Lake
- 4.5.0.1 and later · before 4.5.0.218affected
Phoenix SecureCore™ for Intel Tiger Lake
- 4.3.0.1 and later · before 4.3.0.236affected

Same product

intel: all records

Other highest-scoring records for the same primary product.

CVE-2024-29980Unsafe Handling of IHV UEFI Variables
18Monitor
CVE-2024-29979Unsafe Handling of Phoenix UEFI Variables
18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2024-09-05
Proof-of-concept repository on GitHub	stars:0	2025-08-26

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMay 14, 2024
First PoCSep 5, 2024+113 d
TodayOct 26, 2026+895 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Oren IsacsonEclypsiumfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

Intel® Vulnerability Disclosure Program Intigriti · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

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

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

news.ycombinator.com/item?id=40747852

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records