CVE-2021-3623: Medium severity red hat libtpms vulnerability

Published Jun 28, 2021
·
Updated

A bug was discovered in the libtpms code that may cause access to a buffer beyond the boundary of the buffer or cause failures when trying to resume the state of the vTPM. The vulnerability can be triggered by specially-crafted TPM 2 command packets containing unacceptable/illegal values and those values become an issue when the volatile state of the TPM 2 is marshalled/written or unmarshalled/read. In the former case this can lead to a buffer access beyond its boundary and in the latter case to refusal to accept the state blob due to an illegal value.

To the best of our knowledge, the buffer access beyond its boundaries case does NOT lead to code execution, and as such, any exploitation is likely limited to information leakage and / or denial-of-service (DoS), i.e. a crash. Further, an attacker must have (indirect or direct) access to call TPMLIBVolatileAllStore to exploit this flaw.

Upstream PR: https://github.com/stefanberger/libtpms/pull/223

Upstream fix: https://github.com/stefanberger/libtpms/commit/2f30d62 https://github.com/stefanberger/libtpms/commit/7981d9a https://github.com/stefanberger/libtpms/commit/2e6173c

Other sources

A flaw was found in libtpms. The flaw can be triggered by specially-crafted TPM 2 command packets containing illegal values and may lead to an out-of-bounds access when the volatile state of the TPM 2 is marshalled/written or unmarshalled/read. The highest threat from this vulnerability is to system availability.

MITRE

Affected Software

8 affected componentsFixes available
redhat/libtpms<0.6.5
0.6.5
redhat/libtpms<0.7.8
0.7.8
redhat/libtpms<0.8.4
0.8.4
Libtpms Project Libtpms<0.6.5
Libtpms Project Libtpms>=0.7.0<0.7.8
Libtpms Project Libtpms>=0.8.0<0.8.4
redhat Enterprise Linux=8.0
Fedoraproject Fedora=34

Event History

Mar 2, 2022
CVE Published
via MITRE·10:02 PM
Data Sourced
via MITRE·10:02 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the vulnerability ID for this flaw?

The vulnerability ID is CVE-2021-3623.

2

What is the severity of CVE-2021-3623?

The severity of CVE-2021-3623 is medium (6.1).

3

How can the flaw in libtpms be triggered?

The flaw in libtpms can be triggered by specially-crafted TPM 2 command packets containing illegal values.

4

What is the highest threat from this vulnerability?

The highest threat from this vulnerability is to system integrity.

5

Where can I find more information about CVE-2021-3623?

You can find more information about CVE-2021-3623 on the Red Hat Bugzilla page: https://bugzilla.redhat.com/show_bug.cgi?id=1976806 and on the GitHub commits: https://github.com/stefanberger/libtpms/commit/2e6173c and https://github.com/stefanberger/libtpms/commit/2f30d62.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203