cve.bz

CVE-2019-16863 (TPM-FAIL) st: Observable Discrepancy

5.9 mediumEPSS 3.4%

Known as TPM-FAIL

Medium (5.9) in st. EPSS 3.4% estimated probability of exploitation activity in the next 30 days.

On this page
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
3.4% (unchanged from 3.4% a week ago; 3.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-203 Observable Discrepancy
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-16863 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-16863?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-16863?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-16863 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
st:st33tphf2espi_firmware71.0
st:st33tphf2espi_firmware71.4
st:st33tphf2espi_firmware71.12
st:st33tphf2espi_firmware73.0
st:st33tphf2espi_firmware73.4
st:st33tphf2espi_firmware73.8
st:st33tphf2ei2c_firmware73.5
st:st33tphf2ei2c_firmware73.9
st:st33tphf20spi_firmware74.0
st:st33tphf20spi_firmware74.4
st:st33tphf20spi_firmware74.8
st:st33tphf20spi_firmware74.16
st:st33tphf20i2c_firmware74.5
st:st33tphf20i2c_firmware74.9

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This is a vulnerability in TPM firmware distributed by hardware vendors, not by Red Hat. Red Hat Enterprise Linux exposes the TPM device at /dev/tpm* where it is available for software with the correct privileges to use. Customers are advised to always ensure that firmware updates from hardware vendors are kept up to date with security fixes.

Red Hat's mitigation

To remediate this vulnerability, install relevant firmware updates from your hardware vendor and follow their advice to regenerate keys that may be vulnerable or compromised. STMicroelectronics, Intel and OEMs have published firmware updates and advice at the links provided in the External References section.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6linux-firmwareNot affected
Red Hat Enterprise Linux 7linux-firmwareNot affected
Red Hat Enterprise Linux 8linux-firmwareNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-16863.

Attack patterns (CAPEC)

  • CAPEC-189 Black Box Reverse Engineering Severity: Low
  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON