# CVE-2024-38805: iSCSI Remote Memory Corruption and Denial of Service

> An integer overflow in EDK2 firmware allows remote attackers to cause a denial of service via network means.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **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:** 12 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** DEBIAN-CVE-2024-38805, GHSA-p7wp-52j7-6r5x, GHSA-w8rg-pqpr-83hp, UBUNTU-CVE-2024-38805

## What is CVE-2024-38805?

CVE-2024-38805 is a medium-severity vulnerability in TianoCore EDK2, published on 12 Aug 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 BIOS where a user may cause an Integer Overflow or Wraparound by network means. A successful exploitation of this vulnerability may lead to denial of service.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2024-38805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38805 is a medium-severity vulnerability in TianoCore EDK2, published on 12 Aug 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-38805 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-38805/ (Markdown: https://insights.sbomify.com/CVE-2024-38805/index.md)
```

## Sources

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

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