libtpms returns wrong initialization vector when certain symmetric ciphers are used
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| stefanberger | libtpms | affected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.080% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libtpms Project
Libtpms Project libtpms |
|
| CPEs | cpe:2.3:a:libtpms_project:libtpms:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Libtpms Project
Libtpms Project libtpms |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | libtpms, a library that provides software emulation of a Trusted Platform Module, has a flaw in versions 0.10.0 and 0.10.1. The commonly used integration of libtpms with OpenSSL 3.x contained a vulnerability related to the returned IV (initialization vector) when certain symmetric ciphers were used. Instead of returning the last IV it returned the initial IV to the caller, thus weakening the subsequent encryption and decryption steps. The highest threat from this vulnerability is to data confidentiality. Version 0.10.2 fixes the issue. No known workarounds are available. | |
| Title | libtpms returns wrong initialization vector when certain symmetric ciphers are used | |
| Weaknesses | CWE-327 CWE-330 |
|
| References |
| |
| Metrics |
cvssV3_1
|