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

> A buffer overflow in Phoenix SecureCore UEFI firmware allows attackers to execute arbitrary code or escalate privileges on affected Intel platforms.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-cjqq-r96c-pwrf

## What is CVE-2024-0762?

CVE-2024-0762 is a high-severity memory corruption vulnerability in Phoenix SecureCore™ for Intel Alder Lake, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-0762?

It affects 1 product.


Products: Phoenixtech Securecore Technology.

## How do I fix CVE-2024-0762?

No fix has been published for CVE-2024-0762 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-0762 being exploited?

There is no known exploitation of CVE-2024-0762 in the wild and no public exploit code.

Public exploit code:

- Detecting vulnerabilities like CVE-2024-0762, particularly in UEFI firmware, is quite challenging due to the low-level nature  (github_poc): https://github.com/tadash10/Detect-CVE-2024-0762
- UEFIcanhazbufferoverflow (github_poc): https://github.com/abandon1337/CVE-2024-0762

## Other vulnerabilities in Phoenix SecureCore™ for Intel Alder Lake

- [CVE-2023-31100](https://insights.sbomify.com/CVE-2023-31100/): Missing authorization in SecureCore™ Technology™ 4 (high 8.4)
- [CVE-2023-5058](https://insights.sbomify.com/CVE-2023-5058/): Other in SecureCore™ Technology™ 4 (high 7.8)
- [CVE-2024-1598](https://insights.sbomify.com/CVE-2024-1598/): Potential buffer overflow when handling UEFI variables (high 7.5)
- [CVE-2024-29979](https://insights.sbomify.com/CVE-2024-29979/): Unsafe Handling of Phoenix UEFI Variables (medium 4.6)
- [CVE-2024-29980](https://insights.sbomify.com/CVE-2024-29980/): Unsafe Handling of IHV UEFI Variables (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0762 and fix it if it is affected.

What it is: CVE-2024-0762 is a high-severity memory corruption vulnerability in Phoenix SecureCore™ for Intel Alder Lake, published on 14 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0762 in the wild and no public exploit code.

Affected product: Phoenix SecureCore™ for Intel Alder Lake. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0762/ (Markdown: https://insights.sbomify.com/CVE-2024-0762/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0762
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0762
- OSV: https://osv.dev/vulnerability/CVE-2024-0762

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0762/
Summaries are generated and may contain mistakes; the official description above is the record.