TPM2.0: Out-of-bounds Write
CVE-2023-1017 is a high-severity out-of-bounds write vulnerability in TPM2.0 from Trusted Computing Group, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected TPM2.0 versions: 1.59; 1.38; 1.19. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.38% chance of exploitation within 30 days, higher than 73% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Windows 10 1507 to 10.0.10240.19805 or a later version.
- Update Windows 10 1607 to 10.0.14393.5786 or a later version.
- Update Windows 10 1809 to 10.0.17763.4131 or a later version.
- Read the advisory on trustedcomputinggroup.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Trusted Computing Group | TPM2.0 | 1.59; 1.38; 1.19 | Not stated |
| Trustedcomputinggroup | Trusted Platform Module | 2.0 | Not stated |
| Microsoft | Windows 10 1507 | before 10.0.10240.19805 | 10.0.10240.19805 |
| Microsoft | Windows 10 1607 | before 10.0.14393.5786 | 10.0.14393.5786 |
| Microsoft | Windows 10 1809 | before 10.0.17763.4131 | 10.0.17763.4131 |
| Microsoft | Windows 10 20h2 | before 10.0.19042.2728 | 10.0.19042.2728 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.2728 | 10.0.19044.2728 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.2728 | 10.0.19045.2728 |
| Microsoft | Windows 11 21h2 | before 10.0.22000.1696 | 10.0.22000.1696 |
| Microsoft | Windows 11 22h2 | before 10.0.22621.1413 | 10.0.22621.1413 |
| Microsoft | Windows Server 2016 | before 10.0.14393.5786 | 10.0.14393.5786 |
| Microsoft | Windows Server 2019 | before 10.0.17763.4131 | 10.0.17763.4131 |
| Microsoft | Windows Server 2022 | before 10.0.20348.1607 | 10.0.20348.1607 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
An 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- kb.cert.org/vuls/id/782720Third Party Advisory, US Government Resource
Other references
Other vulnerabilities in TPM2.0
- 7.9 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 8.6 High severity
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.