Skip to content
Fencer Intel
high 7.1

CVE-2020-12946 json

Insufficient input validation in ASP firmware for discrete TPM commands could allow a potential loss of integrity and denial of service.

published 4y ago modified 4mo ago also EUVD-2020-5226

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

Insufficient input validation in ASP firmware for discrete TPM commands could allow a potential loss of integrity and denial of service.

Patch / fix

  • amd epyc_7f72_firmware romepi-sp3_1.0.0.c
  • amd epyc_7f52_firmware romepi-sp3_1.0.0.c
  • amd epyc_7f32_firmware romepi-sp3_1.0.0.c
  • amd epyc_7h12_firmware romepi-sp3_1.0.0.c
  • amd epyc_7742_firmware romepi-sp3_1.0.0.c
  • amd epyc_7702_firmware romepi-sp3_1.0.0.c
  • amd epyc_7702p_firmware romepi-sp3_1.0.0.c
  • amd epyc_7662_firmware romepi-sp3_1.0.0.c
  • amd epyc_7642_firmware romepi-sp3_1.0.0.c
  • amd epyc_7552_firmware romepi-sp3_1.0.0.c
  • amd epyc_7542_firmware romepi-sp3_1.0.0.c
  • amd epyc_7532_firmware romepi-sp3_1.0.0.c
  • amd epyc_7502_firmware romepi-sp3_1.0.0.c
  • amd epyc_7502p_firmware romepi-sp3_1.0.0.c
  • amd epyc_7452_firmware romepi-sp3_1.0.0.c
  • amd epyc_7402_firmware romepi-sp3_1.0.0.c
  • amd epyc_7402p_firmware romepi-sp3_1.0.0.c
  • amd epyc_7352_firmware romepi-sp3_1.0.0.c
  • amd epyc_7302_firmware romepi-sp3_1.0.0.c
  • amd epyc_7302p_firmware romepi-sp3_1.0.0.c

Is CVE-2020-12946 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.6 AV:L/AC:L/Au:N/C:N/I:C/A:C

Affected products

  • AMD Ryzen™ Series
  • AMD Athlon™ Series

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.