libtpms

Every one of the 5 is a mark on the map. Named now: 1 to 5, most at risk first.

1. A flaw was found in the libtpms code that may cause access beyond the boundary of internal buffers. The vulnerability is triggered by specially-crafted TPM2 command packets that t…CVE-2021-3746Libtpms Project · 1.0% likely

   CWE-119

2. A flaw was found in libtpms in versions before 0.8.0. The TPM 2 implementation returns 2048 bit keys with ~1984 bit strength due to a bug in the TCG specification. The bug is in t…CVE-2021-3505Libtpms Project · 0.4% likely

   CWE-331

3. 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 volati…CVE-2021-3623Libtpms Project · 0.3% likely

   CWE-787

4. A stack corruption bug was found in libtpms in versions before 0.7.2 and before 0.8.0 while decrypting data using RSA. This flaw could result in a SIGBUS (bad memory access) and t…CVE-2021-3569Libtpms Project · 0.3% likely

   CWE-120

5. A flaw was found in libtpms in versions before 0.8.2. The commonly used integration of libtpms with OpenSSL contained a vulnerability related to the returned IV (initialization ve…CVE-2021-3446Libtpms Project · 0.1% likely

   CWE-327

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.