CVE-2024-45777 — Grub2: grub-core/gettext: integer overflow leads to heap oob write.
A flaw was found in grub2. The calculation of the translation buffer when reading a language .mo file in grub_gettext_getstr_from_position() may overflow, leading to a Out-of-bound write. This issue can be leveraged by an attacker to overwrite grub2's sensitive heap data, eventually leading to the circumvention of secure boot protections.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Gnu Grub2, Red Hat Enterprise Linux, Red Hat Openshift…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Gnu | Grub2 | ≤ 2.12 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Enterprise Linux | version 7.0version 8.0version 9.0version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Openshift | version 4.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Red Hat Enterprise Linux 10 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Enterprise Linux 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat OpenShift Container Platform 4 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.7 | CVSS 3.1 | Medium | 0.8 | 5.9 | secalert@redhat.com via NIST National Vulnerability Database |
| 6.7 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 6.7 | CVSS 3.1 | Medium | — | — | redhat via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: secalert@redhat.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 21, 2026 → Oct 24, 2026 · 4 reading(s) · max 0.25%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · red hat/red hat openshift container platform 4
- Affected products added · red hat/red hat enterprise linux 9, red hat/red hat enterprise linux 10
- SSVC assessment updated
- Record published
- Affected products added · gnu/grub2, redhat/openshift, redhat/enterprise linux
- CVSS changed · 6.7
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 21, 2026 – Oct 21, 2026
- 1× Official description updated · Oct 21, 2026 – Oct 21, 2026
References
5 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-115486 Open-iscsi: open-iscsi: ipv6 neighbor discovery missing option length validation in iscsiuio allows arp table poisoning 2d
- High CVE-2026-115484 Open-iscsi: open-iscsi: dhcpv4 option parser heap out-of-bounds read in iscsiuio parse_msg 2d
- Medium CVE-2026-115485 Open-iscsi: open-iscsi: dhcpv6 vendor option strlen heap out-of-bounds read and 1-byte write in iscsiuio 2d
- Medium CVE-2026-115221 Ipa: freeipa: freeipa uses subject cn as proof of certificate ownership 2d
- Low CVE-2026-115449 Libslirp: libslirp: icmp echo reply length desynchronization leaks host ip to guest 2d
- Medium CVE-2026-115424 Oc: oc: symlink/hardlink target validation bypass in oc image extract allows file write outside destination 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-45777 is "Grub2: grub-core/gettext: integer overflow leads to heap oob write.", rated Medium. It affects Grub2 (Gnu); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.7 describes technical severity. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.