Analyst readout for executives and security teams
Plain-English summary
GRUB2 can mishandle specially crafted tar file names during early boot. The bug can cause memory corruption and, according to the CVE description, may allow bypassing Secure Boot protections. The practical risk is constrained because exploitation is local and requires high privileges, but successful abuse could undermine a system’s trusted boot guarantees.
Executive priority
Treat this as a targeted boot-chain integrity risk rather than an internet-facing emergency. Prioritize confirmation with platform vendors, especially for high-assurance systems that depend on Secure Boot. Red Hat-listed products in the supplied data are marked unaffected, which lowers urgency for those environments unless local packaging differs.
Technical view
The flaw is an integer overflow in GRUB2 tar filename buffer allocation. A crafted tar file can make the calculated allocation wrap, leading to a heap out-of-bounds write. CVSS 3.1 is 6.7 with local access, low complexity, high privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most relevant to systems that use a vulnerable GRUB2 build and process attacker-controlled tar content in the bootloader path. The supplied Red Hat affected matrix lists RHEL 7, 8, 9, 10, and OpenShift Container Platform 4 as unaffected, so non-Red Hat or differently packaged GRUB2 builds need vendor confirmation.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates local attack with high privileges. The security consequence is serious because the CVE description says exploitation can circumvent Secure Boot protections, but the available evidence does not establish remote or unauthenticated exploitation.
Researcher notes
Key uncertainty is affected build coverage. The bundle names GRUB2 generally but lists Red Hat products as unaffected and does not provide a concrete fixed version. Researchers should focus on vendor-specific GRUB2 packaging, boot media handling, and whether the tar parser is reachable in their boot configuration without assuming broader exposure.
Mitigation direction
- Check your OS or appliance vendor advisory for GRUB2 CVE-2024-45780 status.
- Apply vendor-provided GRUB2 or bootloader updates where the vendor marks systems affected.
- For Red Hat platforms, verify the listed products remain classified as unaffected.
- Limit local administrative, boot media, and bootloader modification access.
- Monitor CVE, Red Hat, and GRUB project updates for revised remediation guidance.
Validation and detection
- Inventory systems using GRUB2 across servers, workstations, appliances, and images.
- Compare installed GRUB2 packages against vendor CVE-2024-45780 advisories.
- Confirm Secure Boot configuration and bootloader trust chain on priority assets.
- Review whether bootloader paths can process untrusted tar content.
- Track KEV status and vendor issue updates for exploitation changes.
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-45780 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9redhatVulnerability scoring details
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2024-45780CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2345856CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.htmlCVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.