CVE-2021-3623
Last modified
CVE-2021-3623 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1976806Issue Tracking, Patch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/2e6173cPatch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/2f30d62Patch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/7981d9aPatch, Third Party Advisory
- https://github.com/stefanberger/libtpms/pull/223Issue Tracking, Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1976806Issue Tracking, Patch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/2e6173cPatch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/2f30d62Patch, Third Party Advisory
- https://github.com/stefanberger/libtpms/commit/7981d9aPatch, Third Party Advisory
- https://github.com/stefanberger/libtpms/pull/223Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2021-3623?
How severe is CVE-2021-3623?
How do I fix CVE-2021-3623?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-3622A flaw was found in the hivex library. This flaw allows an a…4.3
- CVE-2021-36221Go before 1.15.15 and 1.16.x before 1.16.7 has a race condit…5.9
- CVE-2021-36222ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Ce…7.5
- CVE-2021-36224Western Digital My Cloud devices before OS5 have a nobody ac…9.8
- CVE-2021-36225Western Digital My Cloud devices before OS5 allow REST API a…8.8
- CVE-2021-36226Western Digital My Cloud devices before OS5 do not use crypt…9.8
- CVE-2021-36230HashiCorp Terraform Enterprise releases up to v202106-1 did …8.8
- CVE-2021-36231Deserialization of untrusted data in multiple functions in M…8.8
- CVE-2021-36232Improper Authorization in multiple functions in MIK.starligh…8.8
- CVE-2021-36233The function AdminGetFirstFileContentByFilePath in MIK.starl…6.5
- CVE-2021-36234Use of a hard-coded cryptographic key in MIK.starlight 7.9.5…5.5
- CVE-2021-36235An issue was discovered in Ivanti Workspace Control before 1…7.8
Are you affected by CVE-2021-3623?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST