# CVE-2024-45781: Grub2: fs/ufs: oob write in the heap

> An out-of-bounds write in GRUB2's UFS filesystem handler allows attackers to bypass Secure Boot and potentially execute arbitrary code.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-56970, AZL-57064, BELL-CVE-2024-45781, DEBIAN-CVE-2024-45781, GHSA-2xfx-cg6v-cwqv, UBUNTU-CVE-2024-45781

## What is CVE-2024-45781?

CVE-2024-45781 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in grub2. When reading a symbolic link's name from a UFS filesystem, grub2 fails to validate the string length taken as an input. The lack of validation may lead to a heap out-of-bounds write, causing data integrity issues and eventually allowing an attacker to circumvent secure boot protections.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Apply the vendor's patch.

## Is CVE-2024-45781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45781 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 18 Feb 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-45781 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-45781/ (Markdown: https://insights.sbomify.com/CVE-2024-45781/index.md)
```

## Sources

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

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