dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-34302

MEDIUM · 6.7 CVSS v3.1 Published 2022-08-26
Fix available
A fix is available. Upgrade to 2022-06-01 or later.
See remediation →
69/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 flaw was found in New Horizon Datasys bootloaders before 2022-06-01. An attacker may use this bootloader to bypass or tamper with Secure Boot protections. In order to load and execute arbitrary code in the pre-boot stage, an attacker simply needs to replace the existing signed bootloader currently in use with this bootloader. Access to the EFI System Partition is required for booting using external media.

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

The vulnerability in New Horizon Datasys bootloaders prior to June 2022 allows an attacker to replace the existing signed bootloader on the EFI System Partition with a malicious bootloader that bypasses Secure Boot protections, enabling arbitrary code execution in the pre-boot stage.

MitigationUpdate all affected bootloaders to versions released after 2022-06-01 and verify the integrity of Secure Boot configurations; restrict physical access to prevent unauthorized modification of the EFI System Partition.

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
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Uefi BootloaderOperating system
Affected:< 2022-06-01
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 20h2

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 if Horizondatasys UEFI Bootloader is installed
    On Windows: Check the EFI System Partition (typically drive letter E: or F: when mounted) for bootloader files such as bootx64.efi, bootia32.efi, or shimx64.efi and examine their properties for vendor information. On Linux: Mount the EFI System Partition (usually /boot/efi) and list the contents of the EFI directory to identify bootloader files.
    Affected if The EFI System Partition contains bootloader files signed by or associated with Horizondatasys.
  2. Check the Horizondatasys bootloader version or date
    Examine the bootloader file properties or metadata. On Windows, right-click the .efi file and view Details. On Linux, use 'ls -la' or 'file' command on the bootloader in the EFI directory. Compare the file creation or modification date to June 1, 2022.
    Affected if The bootloader file date is prior to 2022-06-01 or the version is older than the June 2022 release.
  3. Verify Secure Boot status
    On Windows: Open System Information and check the 'Secure Boot State' value, or run 'msinfo32' and look for 'Secure Boot State'. On Linux: Run 'mokutil --sb-state' or check '/sys/firmware/efi/efivars/SecureBoot*'.
    Affected if Secure Boot is disabled or in Setup mode, allowing unsigned or modified bootloaders to execute.
  4. Inspect EFI System Partition for unauthorized bootloader files
    Mount the EFI System Partition and compare the bootloader files (bootx64.efi, etc.) against known-good backups or expected hashes. Look for duplicate or unexpected .efi files in the EFI directories.
    Affected if Additional or modified bootloader files exist that were not originally installed, or if the original bootloader has been replaced.

You are affected if the Horizondatasys UEFI Bootloader is present on your system with a version or file date older than June 1, 2022, regardless of Secure Boot status.

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.

From vendor data
Upgrade available Upgrade to 2022-06-01 or later
Fixed in 2022-06-01
Interim mitigation

Update all affected bootloaders to versions released after 2022-06-01 and verify the integrity of Secure Boot configurations; restrict physical access to prevent unauthorized modification of the EFI System Partition.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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