Skip to content
Noroxi
CVE-2022-34301· NVD / CVE Program· CNA mitre

A flaw was found in CryptoPro Secure Disk bootloaders before 2022-06-01.

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.

MediumCVSS 6.7 · v3.1—Proof of concept Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Aug 26, 2022
Updated
Jun 17, 2026
EPSS
1.0% · 61th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

Affected systems

VendorProduct
kidancryptopro securedisk for bitlocker
redhatenterprise linux
microsoftwindows 10
microsoftwindows 11
microsoftwindows 8.1
microsoftwindows rt 8.1
microsoftwindows server 2012
microsoftwindows server 2016
microsoftwindows server 2019
microsoftwindows server 2022

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • microsoft windows server 2012all versions
  • microsoft windows server 2012r2
  • microsoft windows server 2016all versions
  • microsoft windows server 201620h2
  • microsoft windows server 2019all versions
  • microsoft windows server 2022all versions

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9fwupdbefore 1.8.10-2.el9.alma1.8.10-2.el9.alma
AlmaLinux:9fwupd-develbefore 1.8.10-2.el9.alma1.8.10-2.el9.alma
AlmaLinux:9fwupd-plugin-flashrombefore 1.8.10-2.el9.alma1.8.10-2.el9.alma
Red Hat:enterprise_linux:9::appstreamfwupd-debuginfobefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::appstreamfwupd-debugsourcebefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::appstreamfwupd-plugin-flashrombefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::appstreamfwupd-plugin-flashrom-debuginfobefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::appstreamfwupd-tests-debuginfobefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::baseosfwupdbefore 0:1.8.10-2.el90:1.8.10-2.el9
Red Hat:enterprise_linux:9::crbfwupd-develbefore 0:1.8.10-2.el90:1.8.10-2.el9

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:fwupd1.8.10-2.el9.alma · AlmaLinux:9Package registry (OSV)
almalinux:fwupd-devel1.8.10-2.el9.alma · AlmaLinux:9Package registry (OSV)
almalinux:fwupd-plugin-flashrom1.8.10-2.el9.alma · AlmaLinux:9Package registry (OSV)
red hat:fwupd0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:fwupd-debuginfo0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:fwupd-debugsource0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:fwupd-devel0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::crbPackage registry (OSV)
red hat:fwupd-plugin-flashrom0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:fwupd-plugin-flashrom-debuginfo0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:fwupd-tests-debuginfo0:1.8.10-2.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12026-09-07

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1472 d
  3. TodaySep 30, 2026+1496 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records