Secure Boot bypass via tar size overflow
Published Mar 3, 2025 · Updated Jun 29, 2026
Out-of-bounds write in GNU GRUB 2.12 and earlier allows local users to bypass Secure Boot via a crafted tar archive. In grub-core/fs/tar.c, grub_cpio_find_file adds one to 12-digit octal tar header name and link sizes without checking whether grub_size_t wraps before allocating and writing the buffers. High local privileges and control of a tar archive read by GRUB are required; successful exploitation can undermine the boot trust boundary.
Summary
What happened
Out-of-bounds write in GNU GRUB 2.12 and earlier allows local users to bypass Secure Boot via a crafted tar archive. In grub-core/fs/tar.c, grub_cpio_find_file adds one to 12-digit octal tar header name and link sizes without checking whether grub_size_t wraps before allocating and writing the buffers. High local privileges and control of a tar archive read by GRUB are required; successful exploitation can undermine the boot trust boundary.
The record
- CVE
- CVE-2024-45780
- Published
- Mar 3, 2025
- Updated
- Jun 29, 2026
- Vendor
- The GnuPG Project
- Product
- GNU GRUB
- Classifications
- CWE-787, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 3, 2025CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo