CVE-2022-28734
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 · uneditedOut-of-bounds write when handling split HTTP headers; When handling split HTTP headers, GRUB2 HTTP code accidentally moves its internal data buffer point by one position. This can lead to a out-of-bound write further when parsing the HTTP request, writing a NULL byte past the buffer. It's conceivable that an attacker controlled set of packets can lead to corruption of the GRUB2's internal memory metadata.
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 confidenceGRUB2's HTTP handling code has an off-by-one error when parsing split HTTP headers. The internal data buffer pointer is incorrectly advanced by one position, causing an out-of-bounds write of a NULL byte past the end of the buffer. This memory corruption could be exploited via attacker-controlled HTTP packets to compromise GRUB2's internal memory metadata.
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>= 2.00, < 2.06-3all versionsCVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check GRUB2 package versionRun 'grub2-install --version' or 'rpm -q grub2' (RHEL/CentOS) or 'dpkg -l grub-pc' (Debian/Ubuntu) to determine the installed GRUB2 versionAffected if The installed version is >= 2.00 and < 2.06-3 (for Gnu Grub2)
-
Verify if GRUB2 supports HTTP bootCheck if the grub package includes HTTP modules by listing /usr/lib/grub/*/http* or examining the boot configuration files in /boot/grub2/ or /boot/efi/EFI/*/grub.cfg for 'http' or 'network' boot entriesAffected if HTTP modules exist and network boot configurations reference HTTP sources
-
Identify network boot configurationsInspect bootloader configuration files (grub.cfg, grubenv) and check for HTTP boot entries, PXE configuration files, or boot parameters that include http:// URLsAffected if HTTP or network boot paths are configured in the bootloader
-
Check NetApp Active IQ Unified Manager installationIf the product is present, note that all versions are affected regardless of configurationAffected if NetApp Active IQ Unified Manager is installed on the system
A system is affected if it runs Gnu Grub2 version 2.00 through 2.06-2 with HTTP/network boot enabled, or if NetApp Active IQ Unified Manager is installed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.06-3
Update GRUB2 to the patched version provided by your distribution or vendor. For systems with Secure Boot enabled, ensure the updated GRUB2 is properly re-signed and verify the boot chain integrity after patching.
GRUB2 version 2.06-3 or later
- Check current GRUB2 version using: grub2 --version or grub-install --version
- Upgrade GRUB2 to version 2.06-3 or later from your Linux distribution's package manager or upstream source
- If using Secure Boot, rebuild GRUB2 images and re-sign them with appropriate keys
- Verify the upgrade was successful by checking the new version
- For Active IQ Unified Manager: Contact NetApp support for specific patch availability as all versions are affected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28734 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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