CVE-2022-3728
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 · uneditedA 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 confidenceA vulnerability in ThinkPad T14s Gen 3 and X13 Gen 3 allows the BIOS tamper detection mechanism to fail under specific conditions, potentially enabling unauthorized access to the system.
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< 1.30< 1.30CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your ThinkPad modelCheck the laptop label or system information (Windows: win+R, type 'msinfo32'; Linux: dmidecode -s system-product-name)Affected if Model is ThinkPad T14s Gen 3 or ThinkPad X13 Gen 3
-
Check BIOS/firmware versionWindows: Open Lenovo Vantage or BIOS setup (F1 on boot), check BIOS Version under Security or System Information. Linux: sudo dmidecode -s bios-versionAffected if Version number is below 1.30 (e.g., 1.29, 1.28, etc.)
-
Verify tamper detection statusEnter BIOS setup (F1 on boot), navigate to Security menu, look for 'Tamper Detection' or 'BIOS Tamper Detection' settingAffected if Tamper detection is enabled and BIOS version is < 1.30, the protection may not function as intended
If you own a ThinkPad T14s Gen 3 or X13 Gen 3 with BIOS firmware version 1.29 or lower, your tamper detection mechanism may be unreliable.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.30
Apply the Lenovo BIOS/firmware update for affected models. Refer to Lenovo's security advisory for the specific patched BIOS version and update instructions.
Firmware version 1.30
- Check the current BIOS firmware version on the affected ThinkPad T14s Gen 3 or X13 Gen 3 device
- Navigate to the official Lenovo support website (support.lenovo.com) and search for the specific model
- Locate the BIOS update for version 1.30 or later for the respective model
- Download the BIOS update package from Lenovo's official support page
- Follow Lenovo's standard BIOS update procedure (typically requires running the update executable or using Lenovo Vantage)
- Restart the system to complete the firmware update
- Verify the BIOS version has been updated to 1.30 or later after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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