CERT/CC Vulnerability Note VU#782720

Overview

Two buffer overflow vulnerabilities were discovered in the Trusted Platform Module (TPM) 2.0 reference library specification, currently at Level 00, Revision 01.59 November 2019. An attacker who has access to a TPM-command interface can send maliciously-crafted commands to the module and trigger these vulnerabilities. This allows either read-only access to sensitive data or overwriting of normally protected data that is only available to the TPM (e.g., cryptographic keys).

Description

Trusted Platform Module (TPM) technology is a hardware-based solution that provides secure cryptographic functions to the operating systems on modern computers, making it resistant to tampering. As cloud computing and virtualization have become more popular in recent years, software-based TPM implementations have also gained popularity. TPM can be implemented in the form of Discrete, Integrated or Firmware TPM in its hardware form. The virtual TPM's exists in Hypervisor form or in a purely software-based TPM implementation e.g., swtpm. The Trusted Computing Group (TCG) is responsible for maintaining the TPM specifications, which are actively contributed to by both hardware and software manufacturers. The TCG released the TPM 2.0 specifications in October 2014 and has since revised them multiple times. The latest version, Revision 01.59, was released in November 2019. Many TPM hardware and software manufacturers use these specifications to build firmware that complies with standards and provides a secure interface to sensitive cryptographic data. TPM is employed in a variety of devices, from specialized enterprise-grade hardware to Internet of Things (IoT) appliances.

The TPM Library Specification Architecture documents "Session-based encryption" that allows a cryptographic client application to perform various operations, including those that provide Parameter Encryption capabilities. Session-based encryption may be used to ensure confidentiality of these parameters. The operating system or the client software relies on the TPM to securely provide capabilities such as Cipher Feedback (CFB) for block cipher or streaming hash-based XOR obfuscation of the intended parameter payloads.

Quarkslab security researchers found two vulnerabilities in the way the TPM reference specification processes some of these parameters that are part of TPM commands. An Out Of Bound (OOB) read vulnerability in the CryptParameterDecryption() routine allowed a 2-byte read access to data that was not part of the current session. It was also possible to write 2-bytes past the end of the current command buffer resulting in corruption of memory.

An attacker with access to a device built with a vulnerable version of the TPM can trigger this bug by sending crafted commands to the TPM. The vulnerable TPM can thus be tricked to access data that is not part of the intended operation. As the OS relies on the TPM firmware for these functions, it may be difficult to detect or prevent such access using traditional host-based security capabilities.

Impact

An authenticated, local attacker could send maliciously crafted commands to a vulnerable TPM allowing access to sensitive data. In some cases, the attacker can also overwrite protected data in the TPM firmware. This may lead to a crash or arbitrary code execution within the TPM. Because the attacker's payload runs within the TPM, it may be undetectable by other components of the target device.

Solution

Apply an update The Trusted Computing Group (TCG) has released an update to their Errata for TPM2.0 Library Specification with instructions to address these vulnerabilities. To ensure the security of their systems, users should apply any updates provided by hardware and software manufacturers through their supply chain as soon as possible. Updating the firmware of TPM chips may be necessary, and this can be done through an OS vendor or the original equipment manufacturer (OEM). In some cases, the OEM may require resetting the TPM to its original factory default values as part of the update process.

Users in high-assurance computing environments should consider using TPM Remote Attestation to detect any changes to devices and ensure their TPM is tamper proofed. As these attacks involve TPM-based software, mechanisms such as user-password or PIN protection and tpm-totp do not protect against attacks leveraging the vulnerabilities discussed in this article.

Note: the TCG's Errata covers a larger scope and addresses additional security issues beyond the two vulnerabilities discussed in this advisory.

Acknowledgements

Thanks to Francisco Falcon and Ivan Arce of Quarkslab who researched and reported these vulnerabilities, respectively. The TCG and their members worked closely with us and other vendors to coordinate the disclosure of these vulnerabilities. Note that the Immune Gmbh's https://github.com/immune-gmbh/tpm-vuln-checker software has added support for detecting this vulnerability.

This document was written by Vijay Sarvepalli.

Vendor Information

782720

Filter by status:

Filter by content: Additional information available

Sort by:

Expand all

libtpms IBM sponsored Affected

Notified: 2023-01-23 Updated: 2023-08-21

Statement Date: January 23, 2023

CVE-2023-1017

Affected

Vendor Statement:

I agree that the CryptParameterDecryption() function has a potential vulnerability with an out-of-bounds write access since the input buffer per VU #782720.1 lacks proper bounds checking and the input buffer here is also the output buffer.

CVE-2023-1018

Affected

Vendor Statement:

I agree that there's a potential out-of-bounds **read** vulnerability in CryptParameterDecryption() that is due to the usage of BYTE_ARRAY_TO_UINT16(buffer) without prior checking of the bufferSize parameter. if(leadingSizeInByte == 2) { // The first two bytes of the buffer are the size of the // data to be decrypted cipherSize = (UINT32)BYTE_ARRAY_TO_UINT16(buffer); buffer = &buffer[2]; // advance the buffer } #ifdef TPM4B else if(leadingSizeInByte == 4) { // the leading size is four bytes so get the four byte size field cipherSize = BYTE_ARRAY_TO_UINT32(buffer); buffer = &buffer[4]; //advance pointer } #endif else { FAIL(FATAL_ERROR_INTERNAL); } if(cipherSize > bufferSize) return TPM_RC_SIZE; I think before this block there should be a check like this IF TCG wants to stick with the macro: if (bufferSize < leadingSizeInByte) return TPM_RC_SIZE; bufferSize -= leadingSizeInByte; This then also corrects the if(ciphersize > bufferSize) check.

Vendor Statement

I agree that there's a potential out-of-bounds read vulnerability in the CryptParameterDecryption function due to a missing statement checking the input buffer size. Since the input buffer also serves as the output buffer the same function also has an out-of-bounds write vulnerability in the case that the read vulnerability has been triggered.

NetBSD Affected

Notified: 2022-12-01 Updated: 2023-08-21

Statement Date: June 18, 2023

CVE-2023-1017

Affected

CVE-2023-1018

Affected

Vendor Statement

NetBSD is not affected because it not ship the TPM reference implementation or anything based on it.

If NetBSD runs on a machine with a TPM whose firmware is vulnerable, it could used to exploit the TPM, but the same is true of any other operating system running on the same machine. Access to the TPM device node, which is disabled by default, is normally privileged in NetBSD.

pkgsrc users on any operating system may be vulnerable if they have elected to install the security/libtpms or security/swtpm packages and to and expose them to an adversary.

NixOS Affected

Notified: 2022-12-01 Updated: 2023-03-02

Statement Date: March 01, 2023

CVE-2023-1017

Affected

CVE-2023-1018

Affected

Vendor Statement

Fixed in https://github.com/NixOS/nixpkgs/pull/219016 and https://github.com/NixOS/nixpkgs/pull/219049 on 2023-03-01.

We have not received a statement from the vendor.

References

https://trustedcomputinggroup.org/about/security/

Vendor Statement:

Not affected

CVE-2023-1018

Not Affected

Vendor Statement:

Not Affected

Vendor Statement:

Infineon TPM chips are NOT AFFECTED by Issues identified in the TCG's TPM 2.0 Reference Code Implementation (TCGVRT0007 - VU#782720) In more detail: We have access to the details about TCGVRT0007 - VU#782720 concerning the TCG's TPM 2.0 Reference Code Implementation (CVE-2022-45119, CVE-2022-43503). Our Product Security and TPM development teams have already analyzed our product implementations for exposure to these issues and the investigation has concluded with the following results: The reported issues identified in the TCG's TPM 2.0 Reference Code Implementation are NOT affecting our TPM chips, as we have seen in code reviews and also in a practical test. 1. A read attempt attack like reported will result in a TPM error message, blocking that attack path. 2. A write attempt attack like reported is thwarted by the internal data structure of the TPM chip, blocking that attack path. 3. The shortened TPM2B_NAME struct (keySign) will result in a TPM error message, blocking that attack path. 4. A DES key generation is not supported by IFX TPMs, therefore this attack path do not exist. No FW-updates needed or planned!

CVE-2023-1018

Not Affected

Insyde's InsydeH2O and Supervyse products do not contain the affected code.

CVE-2023-1018

Not Affected

Vendor Statement:

Not Affected

Vendor Statement:

Confirmed Lanner's BIOS as well as our TPM chip vendor is not affected by TCGVRT0007 - VU#782720). As stated by our TPM vendor that no FW-updates needed or planned.

LEAD Technologies Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: February 21, 2023

CVE-2023-1017

Not Affected

Vendor Statement:

The LEADTOOLS toolkit does not interact with the TPM module

CVE-2023-1018

Not Affected

Vendor Statement:

References

https://www.multitech.com/documents/publications/policies/SA%2003132023%20-%20CVE-2023-2017_CVE-2023-2018.pdf

Notified: 2022-12-01 Updated: 2023-04-28

Statement Date: April 21, 2023

CVE-2023-1017

Not Affected

Vendor Statement:

To date we have not identified any of our products to be vulnerable by virtue of not leveraging the affected components. We are continuously evaluating and monitoring the situation and will provide an update if and where needed.

CVE-2023-1018

Not Affected

Not Affected

Vendor Statement:

As a software vendor that does not utilize TPM. SolarWinds is not affected.

Splunk Not Affected

Notified: 2022-12-01 Updated: 2024-03-19

Statement Date: March 19, 2024

CVE-2023-1017

Not Affected

CVE-2023-1018

Not Affected

Vendor Statement

We have not received a statement from the vendor.

STMicroelectronics Not Affected

Notified: 2022-11-29 Updated: 2023-04-28

Statement Date: March 10, 2023

CVE-2023-1017

Not Affected

Vendor Statement:

STMicroelectronics confirms that all STMicroelectronics STSAFE-TPM devices are not affected by the issue identified in VU#782720.2 with CVE-2023-1017. The assessment has been conducted by reviewing the code and by testing the STSAFE-TPM products. When the relevant attack paths are performed, the devices return the error code TPM_RC_SIZE and remain fully functional. Some older products may enter failure mode but behave as expected after failure mode exit.

References:

https://www.st.com/resource/en/technical_note/tn1460-stsafetpm-assessment-of-vulnerability-vu782720-stmicroelectronics.pdf

CVE-2023-1018

Not Affected

Vendor Statement:

STMicroelectronics confirms that all STMicroelectronics STSAFE-TPM devices are not affected by the issue identified in VU#782720.2 with CVE-2023-1018. The assessment has been conducted by reviewing the code and by testing the STSAFE-TPM products. When the relevant attack paths are performed, the devices return the error code TPM_RC_INSUFFICIENT and remain fully functional.

References:

https://www.st.com/resource/en/technical_note/tn1460-stsafetpm-assessment-of-vulnerability-vu782720-stmicroelectronics.pdf

Vendor Statement

STMicroelectronics confirms that all STMicroelectronics STSAFE-TPM devices are not affected by the issue identified in VU#782720. No firmware updates are needed.

References

https://www.st.com/resource/en/technical_note/tn1460-stsafetpm-assessment-of-vulnerability-vu782720-stmicroelectronics.pdf

Supermicro Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: December 14, 2022

CVE-2023-1017

Not Affected

Vendor Statement:

Supermicro BIOS is not affected.

CVE-2023-1018

Not Affected

Vendor Statement:

Supermicro BIOS is not affected.

Swann Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: February 22, 2023

CVE-2023-1017

Not Affected

Vendor Statement:

Swann have confirmed that TPM2.0 is not used in hardware or software implementations of our products or related apps.

References:

TPM2.0 is not used in any Swann products or apps.

CVE-2023-1018

Not Affected

Vendor Statement:

Swann have confirmed that TPM2.0 is not used in hardware or software implementations of our products or related apps.

References:

TPM2.0 is not used in any Swann products or apps.

CVE-2023-1018

Not Affected

Vendor Statement:

Not Affected

Vendor Statement:

We do not have any indications at present that any of our supported products are affected by the vulnerability.

Untangle Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: December 15, 2022

CVE-2023-1017

Not Affected

CVE-2023-1018

Not Affected

Vendor Statement

We have not received a statement from the vendor.

VanDyke Software Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: December 09, 2022

CVE-2023-1017

Not Affected

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: December 12, 2022

CVE-2023-1017

Not Affected

https://support.lenovo.com/us/en/product_security/LEN-118320

Modbus Tools Unknown

Notified: 2022-12-01 Updated: 2023-08-21

Statement Date: January 20, 2023

CVE-2023-1017

Unknown

Vendor Statement:

Not affected

CVE-2023-1018

Unknown

Vendor Statement:

Not affected

Navis Unknown

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: January 19, 2023

CVE-2023-1017

Unknown

Vendor Statement:

not related to Navis

CVE-2023-1018

Unknown

Vendor Statement:

Not related to Navis

SmileCDR Unknown

Notified: 2022-12-01 Updated: 2023-02-28

Statement Date: December 02, 2022

CVE-2023-1017

Unknown

Notified: 2022-11-29 Updated: 2023-03-02

CVE-2023-1017

Notified: 2022-12-01 Updated: 2023-02-28

CVE-2023-1017

Unknown

CVE-2023-1018

Unknown

Vendor Statement

We have not received a statement from the vendor.

Software Engineering Institute

CERT Coordination Center

TCG TPM2.0 implementations vulnerable to memory corruption

Vulnerability Note VU#782720

Overview

Description

Impact

Solution

Acknowledgements

Vendor Information

libtpms IBM sponsored Affected

Vendor Statement

NetBSD Affected

Vendor Statement

NixOS Affected

Vendor Statement

References

Parallels Holdings Ltd Affected

Vendor Statement

Red Hat Affected

Vendor Statement

Squid Affected

Vendor Statement

SUSE Linux Affected

Vendor Statement

Trusted Computing Group Affected

Vendor Statement

References

7-Zip.org Not Affected

Vendor Statement

ACROS Security Not Affected

Vendor Statement

ADTRAN Not Affected

Vendor Statement

Advantech Taiwan Not Affected

Vendor Statement

Akamai Technologies Inc. Not Affected

Vendor Statement

AMTELCO Not Affected

Vendor Statement

Analog Devices Inc. Not Affected

Vendor Statement

Android Open Source Project Not Affected

Vendor Statement

Apache Solr Not Affected

Vendor Statement

Applied Informatics GmbH Not Affected

Vendor Statement

ARC Informatique Not Affected

Vendor Statement

Arista Networks Not Affected

Vendor Statement

Artifex Software Inc. Not Affected

Vendor Statement

Aruba Networks Not Affected

Vendor Statement

Atos SE Not Affected

Vendor Statement

Automated Solutions Not Affected

Vendor Statement

AVM GmbH Not Affected

Vendor Statement

Baker Hughes / Bently Nevada Not Affected

Vendor Statement

Baramundi Software Not Affected

Vendor Statement

Bayer Not Affected

Vendor Statement

B. Braun Not Affected

Vendor Statement

Belden Not Affected

Vendor Statement

BIO-ISAC Not Affected

Vendor Statement

BitZipper Not Affected

Vendor Statement

BOSCH Not Affected

Vendor Statement

BR Industrial Automation Not Affected

Vendor Statement