dbcve.org
Thinkpad 25 FirmwareOperating system · Lenovo

CVE-2022-4575

MEDIUM · 6.7 CVSS v3.1 Published 2023-10-30
Fix available
A fix is available. Upgrade to 1.45 / 1.49 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 vulnerability due to improper write protection of UEFI variables was reported in the BIOS of some ThinkPad models could allow an attacker with physical or local access and elevated privileges the ability to bypass Secure Boot.

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

This vulnerability involves improper write protection of UEFI variables in ThinkPad BIOS firmware. Attackers with physical or local access and elevated privileges can modify UEFI variables that should be read-only, enabling them to bypass Secure Boot validation and load untrusted code during the boot process.

MitigationApply the Lenovo BIOS/firmware update for affected ThinkPad models to remediate the improper UEFI variable write protection. Verify Secure Boot remains functional after the update.

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
Thinkpad 25 FirmwareOperating system
Affected:< 1.73
Thinkpad L560 FirmwareOperating system
Affected:< 1.62
Thinkpad P50 FirmwareOperating system
Affected:< 1.71
Thinkpad P50s FirmwareOperating system
Affected:< 1.45
Thinkpad P70 FirmwareOperating system
Affected:< 2.45
Thinkpad T470 FirmwareOperating system
Affected:< 1.73
Thinkpad T470s FirmwareOperating system
Affected:< 1.49
Thinkpad T560 FirmwareOperating system
Affected:< 1.45

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 ThinkPad model
    Run 'dmidecode -s system-product-name' or check system information in BIOS/UEFI setup to confirm the exact ThinkPad model number
    Affected if Model is ThinkPad 25, L560, P50, P50s, P70, T470, T470s, or T560
  2. Check installed BIOS/firmware version
    Run 'dmidecode -s bios-version' or use Lenovo System Update / Vantage to view the current BIOS firmware version
    Affected if Version number is below 1.73 (25/T470), 1.62 (L560), 1.71 (P50), 1.45 (P50s/T560), 2.45 (P70), or 1.49 (T470s)
  3. Verify affected version range
    Compare the installed version against the specific threshold for your model: ThinkPad 25/T470 <1.73, L560 <1.62, P50 <1.71, P50s/T560 <1.45, P70 <2.45, T470s <1.49
    Affected if Installed version falls below the threshold for your specific ThinkPad model
  4. Confirm Secure Boot status
    Check if Secure Boot is enabled in UEFI/BIOS setup or run 'mokutil --sb-state' on Linux
    Affected if Secure Boot is in use (the vulnerability allows bypassing its protection)

Your ThinkPad is affected if it matches one of the eight listed models and the installed BIOS firmware version is below the specified threshold for that model.

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 1.45 / 1.49 / 1.62 or later
Fixed in 1.451.491.62
Interim mitigation

Apply the Lenovo BIOS/firmware update for affected ThinkPad models to remediate the improper UEFI variable write protection. Verify Secure Boot remains functional after the update.

Recommended fix High confidence

Thinkpad 25: >=1.73 | Thinkpad L560: >=1.62 | Thinkpad P50: >=1.71 | Thinkpad P50s: >=1.45 | Thinkpad P70: >=2.45 | Thinkpad T470: >=1.73 | Thinkpad T470s: >=1.49 | Thinkpad T560: >=1.45

  1. Identify your specific ThinkPad model number (e.g., ThinkPad T470)
  2. Visit support.lenovo.com and enter your model number to find the support page
  3. Navigate to the Drivers & Software section
  4. Locate the BIOS update for your specific model
  5. Download the BIOS update file (typically a .exe or .iso file)
  6. Connect the laptop to AC power - do not proceed with BIOS update on battery only
  7. Run the BIOS update executable and follow the on-screen instructions
  8. Allow the system to restart and complete the BIOS update process - do not interrupt this process
Caveat BIOS updates carry risk of rendering the system unusable if interrupted; ensure stable power and do not interrupt the update process

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

Fix this in Thinkpad 25 Firmware 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-4575 — 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-4575 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