CVE-2023-1017
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 write vulnerability exists in TPM2.0's Module Library allowing writing of a 2-byte data past the end of TPM2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can lead to denial of service (crashing the TPM chip/process or rendering it unusable) and/or arbitrary code execution in the TPM context.
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 write vulnerability exists in TPM2.0's Module Library in the CryptParameterDecryption routine, allowing a 2-byte write past the end of a TPM2.0 command buffer. This memory corruption can cause denial of service (TPM chip crash or becoming unusable) and potentially enable arbitrary code execution within the TPM context.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify TPM 2.0 is present and enabledOpen TPM Management (tpm.msc) or run 'Get-Tpm' in PowerShell; confirm TPM Specification Version shows 2.0 and TPM Status shows ReadyAffected if TPM 2.0 is present and enabled - the vulnerability exists in all TPM 2.0 implementations per the Trustedcomputinggroup specification
-
Check Windows versionRun 'winver' or 'systeminfo' from command prompt; note the Windows 10 build number (e.g., 19045) or Windows 11 build number (e.g., 22000)Affected if Windows 10 build < 10240.19805 (1507), < 14393.5786 (1607), < 17763.4131 (1809), < 19042.2728 (20h2), < 19044.2728 (21h2), or < 19045.2728 (22h2); Windows 11 21h2 build < 22000.1696
-
Confirm TPM firmware versionRun 'tpmv2u.exe' from TPM Tools or check via 'Get-TpmChipInfo' in PowerShell; note the firmware version stringAffected if Firmware version is any version of TPM 2.0 - the vulnerability affects the TPM2.0 Module Library implementation itself rather than a specific version number
-
Verify CryptParameterDecryption is in useReview TPM command logs or audit TPM-dependent operations (BitLocker, Windows Hello, certificate operations) - the vulnerability triggers when decrypting TPM command parametersAffected if The system uses TPM 2.0 for encrypted command parameter operations; however, note that the flaw is in the library implementation itself and triggers during normal TPM 2.0 command processing
Your environment is affected if TPM 2.0 is enabled and your Windows version falls below the fixed build numbers, since all TPM 2.0 implementations contain the out-of-bounds write in CryptParameterDecryption.
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 vendor-specific TPM firmware updates or patches to the TPM2.0 Module Library; verify TPM functionality post-update to ensure the vulnerability is remediated without breaking TPM-dependent operations.
Windows 10 1507: 10.0.10240.19805 or later | Windows 10 1607: 10.0.14393.5786 or later | Windows 10 1809: 10.0.17763.4131 or later | Windows 10 20h2: 10.0.19042.2728 or later | Windows 10 21h2: 10.0.19044.2728 or later | Windows 10 22h2: 10.0.19045.2728 or later | Windows 11 21h2: 10.0.22000.1696 or
- Open Windows Update Settings (Settings > Update & Security > Windows Update)
- Click 'Check for updates' to download and install the latest security updates
- Verify the update was installed by checking the Windows update history
- Restart the system to ensure TPM firmware/driver updates are fully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1017 — 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-1017 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