# CVE-2024-38797: Out-of-bounds Read in HashPeImageByType()

> An out-of-bounds read in EDK2 allows attackers to cause integrity loss or denial of service via corrupted network data.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** DEBIAN-CVE-2024-38797, GHSA-4wjw-6xmf-44xf, OESA-2025-1503, UBUNTU-CVE-2024-38797

## What is CVE-2024-38797?

CVE-2024-38797 is a medium-severity memory corruption vulnerability in TianoCore EDK2, published on 7 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EDK2 contains a vulnerability in the HashPeImageByType(). A user may cause a read out of bounds when a corrupted data pointer and length are sent via an adjecent network. A successful exploit of this vulnerability may lead to a loss of Integrity and/or Availability.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2024-38797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38797 is a medium-severity memory corruption vulnerability in TianoCore EDK2, published on 7 Apr 2025. 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-38797 in the wild and no public exploit code.

Affected product: TianoCore EDK2. 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-38797/ (Markdown: https://insights.sbomify.com/CVE-2024-38797/index.md)
```

## Sources

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

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