dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-34301

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 CryptoPro Secure Disk 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 · high confidence

A vulnerability in CryptoPro Secure Disk bootloaders allows an attacker to bypass Secure Boot protections by replacing the existing signed bootloader with a malicious one, enabling arbitrary code execution in the pre-boot stage. The attack requires physical access or access to the EFI System Partition to replace the bootloader file.

MitigationUpdate CryptoPro Secure Disk bootloaders to a version released after 2022-06-01 that contains the security fix, and verify Secure Boot integrity configurations.

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
Cryptopro Securedisk For BitlockerOperating 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. Determine if CryptoPro Secure Disk software is installed
    On Windows, check Program Files for CryptoPro folders or review installed programs list. On Linux, query package manager for cryptopro packages (rpm -qa | grep -i crypto or dpkg -l | grep -i crypto).
    Affected if CryptoPro Secure Disk software is present on the system
  2. Identify the installed CryptoPro Secure Disk version
    Check the software version through its UI, registry (HKLM\SOFTWARE\Crypto Pro\Disk), or by examining the bootloader files themselves. For Windows, inspect the executable version info. For Linux, check rpm or dpkg package version.
    Affected if The version is older than the 2022-06-01 release or cannot be determined (unknown versions may be pre-fix)
  3. Locate CryptoPro bootloaders on the EFI System Partition
    Mount the EFI System Partition (typically drive letter E: or mount point /boot/efi/EFI) and examine the \CryptoPro or similar directory structure. List all .efi bootloader files in the EFI folder.
    Affected if CryptoPro .efi bootloader files exist in the EFI System Partition and the version is vulnerable
  4. Verify integrity and timestamps of bootloader files
    Compare cryptographic hashes (SHA256) of existing CryptoPro .efi files against known-good baseline values if available. Alternatively, check file modification timestamps for unexpected changes.
    Affected if Bootloader files have been modified, show unexpected timestamps, or differ from expected hashes
  5. Confirm Secure Boot status
    Use system utilities: on Windows run 'msinfo32' and check 'Secure Boot State'; on Linux check 'mokutil --sb-state' or review UEFI firmware settings.
    Affected if Secure Boot is disabled (the vulnerability bypasses Secure Boot, but the attack surface is higher when Secure Boot is enabled but bypassed)

The environment is affected if CryptoPro Secure Disk is installed with a bootloader version released before 2022-06-01, or if unauthorized bootloader files are present on the EFI System Partition, 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.

dbcve · scoped
Upgrade available Upgrade to 2022-06-01 or later
Fixed in 2022-06-01
Interim mitigation

Update CryptoPro Secure Disk bootloaders to a version released after 2022-06-01 that contains the security fix, and verify Secure Boot integrity configurations.

Recommended fix High confidence

CryptoPro Secure Disk version >= 2022-06-01

  1. Identify the current version of CryptoPro Secure Disk installed on the affected system
  2. Download CryptoPro Secure Disk version released on or after 2022-06-01 from the official CryptoPro vendor
  3. Apply the upgrade following the vendor's documented upgrade procedure
  4. Reboot the system to ensure the new bootloader is loaded
  5. Verify the bootloader version post-upgrade to confirm the fix is applied
  6. Ensure Secure Boot remains enabled and functioning correctly
Caveat Review CryptoPro release notes for any compatibility or configuration changes between versions

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

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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