CVE-2023-1018
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 · uneditedAn out-of-bounds read vulnerability exists in TPM2.0's Module Library allowing a 2-byte read past the end of a TPM2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can read or access sensitive data stored in the TPM.
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 confidenceAn out-of-bounds read vulnerability in TPM 2.0's Module Library allows a 2-byte read past the end of a TPM2.0 command buffer in the CryptParameterDecryption routine, potentially exposing sensitive data stored in the TPM.
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= 2.0< 10.0.10240.19805< 10.0.14393.5786< 10.0.17763.4131< 10.0.19042.2728< 10.0.19044.2728< 10.0.19045.2728< 10.0.22000.1696CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm TPM 2.0 is present and enabledOpen Task Manager > Security tab, or run 'Get-Tpm' in PowerShell, or check tpm.mscAffected if TPM is present and shows as TPM 2.0 (not TPM 1.2)
-
Check Windows version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"'Affected if Build number is less than 10.0.10240.19805 (1507), 10.0.14393.5786 (1607), 10.0.17763.4131 (1809), 10.0.19042.2728 (20H2), 10.0.19044.2728 (21H2), 10.0.19045.2728 (22H2), or 10.0.22000.1696 (Win11 21H2)
-
Check TPM firmware versionRun 'Get-Tpm' in PowerShell to retrieve TPM manufacturer and version, or use manufacturer-provided TPM toolsAffected if TPM 2.0 firmware is present without the CVE-2023-1018 firmware update from the hardware vendor
-
Verify CryptParameterDecryption is in useThis is a TPM internal operation. Check if TPM-based encryption features are enabled, such as Windows Hello, BitLocker with TPM protector, or any application using TPM2_Unseal. Review event logs for unusual TPM command activity.Affected if TPM 2.0 is actively being used for cryptographic operations that involve parameter decryption
System is affected if TPM 2.0 is present and enabled AND the Windows build is below the patched versions listed, or if TPM 2.0 firmware has not been updated to address CVE-2023-1018.
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 · scoped10.0.10240.1980510.0.14393.578610.0.17763.4131
Apply TPM firmware updates from the hardware vendor that address CVE-2023-1018; until patched, limit physical and administrative access to systems with affected TPM implementations to reduce exploitation risk.
Windows 10 1507 to build >=10.0.10240.19805; Windows 10 1607 to build >=10.0.14393.5786; Windows 10 1809 to build >=10.0.17763.4131; Windows 10 20h2 to build >=10.0.19042.2728; Windows 10 21h2 to build >=10.0.19044.2728; Windows 10 22h2 to build >=10.0.19045.2728; Windows 11 21h2 to build >=10.0.220
- Identify the current Windows version by running 'winver' or checking System Information
- Apply the appropriate Windows Security Update for your specific Windows version: For Windows 10 1507, upgrade to build 10.0.10240.19805 or later; For Windows 10 1607, upgrade to build 10.0.14393.5786 or later; For Windows 10 1809, upgrade to build 10.0.17763.4131 or later; For Windows 10 20h2, upgrade to build 10.0.19042.2728 or later; For Windows 10 21h2, upgrade to build 10.0.19044.2728 or later
- Install the latest Windows Security Updates via Windows Update or manually download from Microsoft Update Catalog
- Restart the system after applying the update to ensure TPM firmware components are properly updated
- Verify the patch was applied by checking the installed Windows build version matches or exceeds the fixed versions listed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-1018 — 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-2023-1018 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