CVE-2019-6188
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 · uneditedThe BIOS tamper detection mechanism was not triggered in Lenovo ThinkPad T460p, BIOS versions up to R07ET90W, and T470p, BIOS versions up to R0FET50W, which may allow for 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 · high confidenceThe BIOS tamper detection mechanism on Lenovo ThinkPad T460p (versions up to R07ET90W) and T470p (versions up to R0FET50W) fails to trigger, allowing physical tampering with the system to go undetected and potentially enabling unauthorized access.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 Lenovo modelCheck the system label or use systeminfo (Windows) or dmidecode (Linux) to confirm the exact model name (e.g., ThinkPad T460p, T470p, Ideacentre 510, etc.)Affected if Model is T460p, T470p, or any Ideacentre/510 model listed in the affected products
-
Check BIOS version on ThinkPad T460pRun 'wmic bios get smbiosbiosversion' (Windows) or 'dmidecode -s bios-version' (Linux). Compare the version string to R07ET90W.Affected if Version is at or below R07ET90W on a T460p
-
Check BIOS version on ThinkPad T470pRun 'wmic bios get smbiosbiosversion' (Windows) or 'dmidecode -s bios-version' (Linux). Compare the version string to R0FET50W.Affected if Version is at or below R0FET50W on a T470p
-
Check BIOS version on Ideacentre or 510 modelsRun 'wmic bios get smbiosbiosversion' (Windows) or 'dmidecode -s bios-version' (Linux). All versions of these models are affected.Affected if Model is any Ideacentre 300/310 or Ideacentre 510 variant listed, regardless of version
-
Verify tamper detection status (if accessible)Access BIOS/UEFI setup (press Enter or F1 during boot) and look for 'Tamper Detection' or 'Anti-theft' settings under Security menu. Note that the flaw may prevent detection even if settings appear enabled.Affected if Settings indicate tamper detection is enabled but you cannot confirm it triggered after physical access events
You are affected if you own a T460p with BIOS R07ET90W or earlier, a T470p with BIOS R0FET50W or earlier, or any of the Ideacentre/510 models listed, as the tamper detection mechanism can fail to trigger upon physical tampering.
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.
From vendor dataUpdate BIOS to a patched version beyond R07ET90W for T460p and R0FET50W for T470p when released, or implement compensating physical security controls until the update is available.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6188 — 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-2019-6188 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