CVE-2024-45781: Grub2: fs/ufs: oob write in the heap
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.
Security readout for executives and security teams
Plain-English summary
This vulnerability is in GRUB2, the bootloader used before Linux starts. A malformed UFS symbolic link name can cause a heap out-of-bounds write. The main business concern is boot-chain integrity: Red Hat says this could eventually help bypass Secure Boot, but it requires local, high-privilege conditions.
Executive priority
Treat as a moderate-priority boot-chain integrity issue. It is not shown as actively exploited, and it requires high local privileges, but remediation matters for regulated, high-trust, or Secure Boot-dependent environments.
Technical view
GRUB2’s UFS filesystem code fails to validate a string length when reading a symbolic link name. The issue is classified as CWE-787 and scored CVSS 6.7 with local attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears concentrated in affected Red Hat GRUB2 and RHCOS builds. The bundle lists RHEL 9, RHEL 10, and OpenShift Container Platform 4 as affected. RHEL 7 and 8 status is unknown. Practical exposure depends on GRUB2 processing a malicious UFS filesystem during boot.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. The CVSS vector requires local access and high privileges, which lowers broad remote-risk urgency but does not remove concern for systems where Secure Boot trust is critical.
Researcher notes
Key constraints are the local attack vector, high privileges required, and the UFS symlink parsing path in GRUB2. Evidence supports potential Secure Boot bypass impact, but the bundle does not provide exploit maturity, patch mechanics, or affected non-Red Hat distributions.
Mitigation direction
Apply applicable Red Hat advisories RHSA-2025:6990 or RHSA-2025:16154 where relevant.
Check Red Hat’s CVE page for current fixed package guidance.
Prioritize bootloader updates on Secure Boot and high-assurance systems.
Limit high-privileged local access to boot configuration and boot media.
Track RHEL 7 and 8 status because the bundle lists them as unknown.
Validation and detection
Inventory GRUB2 package versions across RHEL and RHCOS systems.
Compare installed versions with Red Hat advisory and CVE guidance.
Confirm OpenShift nodes use remediated RHCOS content when applicable.
Verify Secure Boot and bootloader update processes remain intact after patching.
Record exceptions where vendor status is unknown or updates are unavailable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
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.
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.
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.
1CVSS vectors
5Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.