dbcve.org
Thinkpad T14s Gen 3 FirmwareOperating system · Lenovo

CVE-2022-48182

MEDIUM · 6.8 CVSS v3.1 Published 2023-10-09
Fix available
A fix is available. Upgrade to 1.30 / 1.35 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 was reported in ThinkPad T14s Gen 3 and X13 Gen3 that could cause the BIOS tamper detection mechanism to not trigger under specific circumstances which could allow unauthorized access.

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

A vulnerability in ThinkPad T14s Gen 3 and X13 Gen 3 BIOS prevents the tamper detection mechanism from triggering under specific circumstances, potentially allowing unauthorized physical access to the affected systems.

MitigationApply the Lenovo BIOS/firmware update for the affected ThinkPad models to restore proper tamper detection functionality.

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 T14s Gen 3 FirmwareOperating system
Affected:< 1.30< 1.35
Thinkpad X13 Gen 3 FirmwareOperating system
Affected:< 1.30< 1.35

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

CVSS:3.1/AV:P/AC:L/PR:N/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. Confirm your ThinkPad model
    Identify the exact model number of your system (typically found on the bottom chassis label, in BIOS setup, or via system information utilities)
    Affected if The model is not Lenovo ThinkPad T14s Gen 3 or X13 Gen 3, then this CVE does not apply
  2. Locate the BIOS firmware version
    Access BIOS setup (press Enter or F1 during boot), check the BIOS version information page; alternatively, use system information tools like 'msinfo32' on Windows or 'dmidecode' on Linux to retrieve BIOS version
    Affected if Cannot retrieve BIOS version - detection cannot proceed
  3. Compare installed version to affected ranges
    Note the BIOS version displayed (format typically like 1.xx) and compare against the affected version thresholds: versions below 1.30 or versions below 1.35
    Affected if The installed BIOS version is below 1.30 or below 1.35 (the exact threshold depends on the specific BIOS branch); versions 1.30 and above and 1.35 and above are not affected

You are affected if your system is a Lenovo ThinkPad T14s Gen 3 or X13 Gen 3 running BIOS firmware version lower than 1.30 or lower than 1.35, as those versions contain the tamper detection bypass flaw.

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.30 / 1.35 or later
Fixed in 1.301.35
Interim mitigation

Apply the Lenovo BIOS/firmware update for the affected ThinkPad models to restore proper tamper detection functionality.

Recommended fix Moderate confidence

BIOS firmware version 1.30 or later (or 1.35 or later, depending on your firmware branch)

  1. 1. Identify your ThinkPad model number (T14s Gen 3 or X13 Gen 3) and current BIOS version by running 'msinfo32' or checking BIOS setup (F1 on boot)
  2. 2. Visit support.lenovo.com and search for your specific ThinkPad model
  3. 3. Navigate to the Drivers & Software section and locate BIOS updates
  4. 4. Download the latest BIOS firmware update package (version 1.30 or 1.35 or higher, depending on your current baseline)
  5. 5. Run the BIOS update utility as Administrator, or if instructed, create a bootable USB update media
  6. 6. Follow the on-screen prompts and ensure the laptop remains powered on during the update process
  7. 7. After the update completes, restart the system and verify the new BIOS version in BIOS setup or via 'msinfo32'
Caveat BIOS updates carry a risk if interrupted; ensure laptop is plugged into power and do not shut down during the update process

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

Fix this in Thinkpad T14s Gen 3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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