vTPM crash via retained oversized buffer length
Published Mar 2, 2022 · Updated Aug 3, 2024
Out-of-bounds access in libtpms allows local users to crash a vTPM through crafted TPM 2 command packets containing illegal values. Failed TPM2B unmarshalling leaves illegal size values in memory, and TPMLIB_VolatileAll_Store later marshals them without a maximum-size check. Exploitation requires direct or indirect access to that API; the documented scope is limited to a crash or information leakage rather than code execution.
Summary
What happened
Out-of-bounds access in libtpms allows local users to crash a vTPM through crafted TPM 2 command packets containing illegal values. Failed TPM2B unmarshalling leaves illegal size values in memory, and TPMLIB_VolatileAll_Store later marshals them without a maximum-size check. Exploitation requires direct or indirect access to that API; the documented scope is limited to a crash or information leakage rather than code execution.
The record
- CVE
- CVE-2021-3623
- Published
- Mar 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- libtpms Project
- Product
- libtpms
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed-In - libtpms 0.6.5, libtpms 0.7.8, libtpms 0.8.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo