dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-45782

HIGH · 7.8 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to after 2.12 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in the HFS filesystem. When reading an HFS volume's name at grub_fs_mount(), the HFS filesystem driver performs a strcpy() using the user-provided volume name as input without properly validating the volume name's length. This issue may read to a heap-based out-of-bounds writer, impacting grub's sensitive data integrity and eventually leading to a secure boot protection bypass.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in GRUB2's HFS filesystem driver. The grub_fs_mount() function uses strcpy() to copy a user-provided HFS volume name into a fixed-size buffer without validating the volume name's length, allowing an attacker to overwrite adjacent heap memory and potentially bypass Secure Boot protections.

MitigationReplace the unsafe strcpy() call in grub_fs_mount() with a bounds-checked string copy function (e.g., strncpy() or a similar safe string handling function) and add explicit length validation before copying the volume name. Alternatively, disable HFS filesystem support in GRUB if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Grub2Application
Affected:<= 2.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GRUB2 version
    Run 'grub2-install --version' or check the installed grub2 package version using your distribution's package manager (e.g., 'rpm -q grub2' for RHEL-based systems)
    Affected if The installed GRUB2 version is 2.12 or lower, or the version cannot be determined but GRUB2 is present
  2. Verify HFS filesystem support in GRUB
    Check if the HFS filesystem module is loaded or available in GRUB. On RHEL systems, examine /boot/grub2/i386-pc/ or /boot/efi/EFI/*/fonts/ for hfs*.mod files, or list installed GRUB modules with 'ls /boot/grub2/i386-pc/*.mod | grep -i hfs'
    Affected if HFS-related modules (such as hfs, hfsplus, or hfsutils) are present in the GRUB modules directory, indicating HFS support is compiled or configured
  3. Check for HFS filesystems in use
    Run 'mount | grep -E "hfs|hfsplus"' to list any currently mounted HFS volumes, or check /etc/fstab for HFS entries
    Affected if Any HFS or HFS+ filesystems are mounted or configured on the system, providing a potential attack vector for the vulnerable driver
  4. Inspect GRUB configuration for HFS volume handling
    Review GRUB config files in /boot/grub2/grub.cfg or /boot/efi/EFI/*/grub.cfg for commands that reference HFS volumes, particularly any 'search' or 'set root' commands pointing to HFS devices
    Affected if The GRUB configuration references HFS volumes or uses HFS-related search or partition commands
  5. Confirm GRUB2 package vendor and support status
    If running Red Hat Enterprise Linux or OpenShift Container Platform, verify the exact version with 'cat /etc/redhat-release' and check if the system receives vendor support for GRUB2 security updates
    Affected if The system runs RHEL 7.0, 8.0, 9.0, or OpenShift Container Platform 4.0 and the GRUB2 package has not been patched by the vendor

A system is affected if it runs GRUB2 version 2.12 or lower with HFS filesystem support enabled or HFS volumes configured, particularly on RHEL 7.0-9.0 or OCP 4.0 environments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.12
Interim mitigation

Replace the unsafe strcpy() call in grub_fs_mount() with a bounds-checked string copy function (e.g., strncpy() or a similar safe string handling function) and add explicit length validation before copying the volume name. Alternatively, disable HFS filesystem support in GRUB if not required.

Recommended fix Moderate confidence

Grub2 version > 2.12 (specific fixed version varies by distribution; consult your Linux vendor's security advisory)

  1. Update the grub2 package to a version newer than 2.12 to receive the security fix for the HFS filesystem driver vulnerability
  2. On RHEL/CentOS systems, run: yum update grub2 or dnf update grub2
  3. On RHEL 7/8/9 systems, also update grubby and shim packages: yum update grubby shim-x64
  4. After updating, regenerate grub configuration if necessary: grub2-mkconfig -o /boot/grub2/grub.cfg (or /boot/efi/EFI/*/grub.cfg for UEFI systems)
  5. Reboot the system to load the updated grub2 bootloader
  6. Verify the installed grub2 version is greater than 2.12: grub2-install --version
Caveat Minor: Ensure boot configuration compatibility after grub update; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45782 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data