dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-45778

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to after 2.12 or later.
See remediation →
57/100
Remediation priority · Elevated
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 stack overflow flaw was found when reading a BFS file system. A crafted BFS filesystem may lead to an uncontrolled loop, causing grub2 to crash.

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 · moderate confidence

A stack overflow vulnerability exists in GRUB2's BFS (BeOS File System) driver when parsing crafted BFS filesystems. The vulnerability stems from an uncontrolled loop during filesystem parsing, which leads to stack exhaustion and ultimately causes GRUB2 to crash.

MitigationAvoid mounting untrusted BFS filesystems; update to patched GRUB2 versions when available; validate filesystem images before use.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 package version using your system's package manager (e.g., 'rpm -q grub2' for RHEL, 'dpkg -l grub2' for Debian)
    Affected if The installed version is 2.12 or earlier, or if the version cannot be determined and falls within the vulnerable range
  2. Check if BFS filesystem module exists
    Look for the bfs.mod module in the GRUB2 modules directory, typically found at /usr/lib/grub/x86_64-redhat/ or /boot/grub/x86_64-efi/
    Affected if The bfs.mod module is present on the system, indicating BFS support is compiled or installed
  3. Verify BFS module loading capability
    Check GRUB2 configuration for module loading directives or verify the module is loadable by running 'grub2-mkimage -O x86_64-efi -o /tmp/test.img bfs' to confirm BFS module availability
    Affected if GRUB2 can load or has loaded the BFS module at any point
  4. Identify BFS filesystem exposure
    Search for BFS filesystem images or partitions: run 'lsblk -f' to list filesystems, 'file -s /dev/sd*' to identify BFS type, and find BFS image files using 'find / -name '*.bfs' -o -name '*bfs*' 2>/dev/null'
    Affected if Any BFS filesystems or BFS-formatted images exist on the system or are accessible to GRUB2 during boot

A system is affected if it runs a vulnerable GRUB2 version (2.12 or earlier) AND has the BFS filesystem module available, with potential exposure to untrusted BFS filesystems during the boot process.

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

Avoid mounting untrusted BFS filesystems; update to patched GRUB2 versions when available; validate filesystem images before use.

Recommended fix Moderate confidence

Grub2 version greater than 2.12 (specific version varies by distribution - consult vendor security advisories for RHEL 7/8/9 and OCP 4.0 for exact fixed versions)

  1. Identify the current Grub2 version installed on affected systems using: rpm -q grub2 or dpkg -l | grep grub
  2. For RHEL/CentOS systems: yum update grub2 or dnf update grub2
  3. For OpenShift Container Platform: Update through the OCP update path to a version containing the Grub2 fix
  4. After updating grub2 package, regenerate grub.cfg using: grub2-mkconfig -o /boot/grub2/grub.cfg (or /boot/efi/EFI/*/grub.cfg for UEFI systems)
  5. Reboot systems to load the updated bootloader
  6. Verify the new Grub2 version is loaded post-reboot using: grub2 --version
Caveat Bootloader updates carry inherent risk; ensure backups of boot configuration and EFI/NVRAM settings exist before updating, and test in non-production environments first

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

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45778 — 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-45778 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