amd epyc 7313 firmware
ProduktUScpe:2.3:o:amd:epyc_7313_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
5critical37high43medium3low
aktualisiert 2026-10-27
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2024-21978US | high7.9 | 0.49% (42nd) | Exploit | ✓milanpi_1.0.0.d | 2024-08-05 | < milanpi_1.0.0.d |
| CVE-2024-21980US | high7.9 | 0.45% (39th) | Exploit | ✓milanpi_1.0.0.d | 2024-08-05 | < milanpi_1.0.0.d |
| CVE-2023-31355US | medium6.0 | 0.44% (38th) | Exploit | ✓milanpi_1.0.0.d | 2024-08-05 | < milanpi_1.0.0.d |
| CVE-2023-31346US | medium6.0 | 0.31% (24th) | Exploit | ✓milanpi_1.0.0.c | 2024-02-13 | < milanpi_1.0.0.c |
| CVE-2023-20573US | low3.2 | 0.29% (21st) | Exploit | ✗kein Fix | 2024-01-11 | — |
| CVE-2023-20569US | medium4.7 | 7.30% (94th) | — | ✓milanpi_1.0.0.c | 2023-08-08 | < milanpi_1.0.0.c |
| CVE-2021-26322US | high7.5OT erhöht | 1.05% (64th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2020-12988US | high7.5 | 1.04% (64th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-06-11 | < milanpi-sp3_1.0.0.4 |
| CVE-2023-20592US | medium6.5 | 1.02% (63rd) | — | ✓milanpi_1.0.0.c | 2023-11-14 | < milanpi_1.0.0.c |
| CVE-2021-26338US | high7.5 | 0.93% (60th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2023-20575US | medium6.5 | 0.80% (57th) | — | ✗kein Fix | 2023-07-11 | — |
| CVE-2023-20520US | critical9.8 | 0.79% (56th) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.5 |
| CVE-2021-46769US | high8.8 | 0.78% (56th) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2021-26379US | critical9.8 | 0.68% (52nd) | — | ✓milanpi_1.0.0.9 | 2023-05-09 | < milanpi_1.0.0.9 |
| CVE-2021-46756US | critical9.1 | 0.65% (51st) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2023-20531US | high7.5 | 0.63% (50th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2023-20530US | high7.5 | 0.63% (50th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2023-20529US | high7.5 | 0.63% (50th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2021-46764US | high7.5 | 0.63% (50th) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2023-20527US | medium6.5 | 0.61% (49th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2023-20525US | medium6.5 | 0.61% (49th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2022-23824US | medium5.5 | 0.60% (48th) | — | ✗kein Fix | 2022-11-09 | — |
| CVE-2023-20532US | medium5.3 | 0.57% (47th) | — | ✓milanpi_1.0.0.5 | 2023-01-11 | < milanpi_1.0.0.5 |
| CVE-2021-46774US | high7.5 | 0.51% (43rd) | — | ✓milanpi_1.0.0.b | 2023-11-14 | < milanpi_1.0.0.b |
| CVE-2022-23818US | high7.5 | 0.50% (43rd) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2023-20533US | high7.5 | 0.50% (43rd) | — | ✓milanpi_1.0.0.5 | 2023-11-14 | < milanpi_1.0.0.5 |
| CVE-2023-20524US | high7.5 | 0.49% (42nd) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.5 |
| CVE-2021-46763US | high7.5 | 0.49% (42nd) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2023-31347US | medium4.9 | 0.46% (40th) | — | ✓milanpi_1.0.0.c | 2024-02-13 | < milanpi_1.0.0.c |
| CVE-2021-26345US | medium4.9 | 0.43% (38th) | — | ✓milanpi_1.0.0.a | 2023-11-14 | < milanpi_1.0.0.a |
| CVE-2021-26356US | high7.4 | 0.40% (34th) | — | ✓milanpi_1.0.0.6 | 2023-05-09 | < milanpi_1.0.0.6 |
| CVE-2023-20566US | high7.5 | 0.37% (30th) | — | ✓milanpi_1.0.0.b | 2023-11-14 | < milanpi_1.0.0.b |
| CVE-2021-46762US | critical9.1 | 0.35% (28th) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2022-23830US | medium5.3 | 0.35% (28th) | — | ✓milanpi_1.0.0.a | 2023-11-14 | < milanpi_1.0.0.a |
| CVE-2020-12944US | high7.8 | 0.35% (28th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-46744US | medium6.5 | 0.33% (27th) | — | ✗kein Fix | 2022-05-11 | — |
| CVE-2021-46775US | medium6.8 | 0.32% (25th) | — | ✗kein Fix | 2023-05-09 | = milanpi_1.0.0.9 |
| CVE-2020-12966US | medium5.5 | 0.31% (24th) | — | ✓milanpi-sp3_1.0.0.5 | 2022-02-04 | < milanpi-sp3_1.0.0.5 |
| CVE-2023-20526US | medium4.6 | 0.31% (24th) | — | ✓milanpi_1.0.0.5 | 2023-11-14 | < milanpi_1.0.0.5 |
| CVE-2021-46771US | high7.8 | 0.30% (23rd) | — | ✓milanpi-sp3_1.0.0.4 | 2022-05-10 | < milanpi-sp3_1.0.0.4 |
| CVE-2023-20591US | critical10.0 | 0.30% (22nd) | — | ✓milanpi_1.0.0.b | 2024-08-13 | < milanpi_1.0.0.b |
| CVE-2021-26335US | high7.8 | 0.29% (22nd) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-26331US | high7.8 | 0.29% (22nd) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-26339US | medium5.5 | 0.28% (20th) | — | ✓milanpi-sp3_1.0.0.7 | 2022-05-11 | < milanpi-sp3_1.0.0.7 |
| CVE-2021-26353US | high7.8 | 0.27% (19th) | — | ✓milanpi-sp3_1.0.0.4 | 2022-05-10 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-26324US | high7.8 | 0.27% (19th) | — | ✓milanpi-sp3_1.0.0.4 | 2022-05-10 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-26316US | high7.8 | 0.27% (19th) | — | ✓milanpi-sp3_1.0.0.8 | 2023-01-11 | < milanpi-sp3_1.0.0.8 |
| CVE-2023-20521US | medium5.7 | 0.26% (18th) | — | ✓milanpi_1.0.0.7 | 2023-11-14 | < milanpi_1.0.0.7 |
| CVE-2021-26326US | high7.8 | 0.26% (18th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
| CVE-2021-26321US | medium5.5 | 0.25% (17th) | — | ✓milanpi-sp3_1.0.0.4 | 2021-11-16 | < milanpi-sp3_1.0.0.4 |
50 von 88 angezeigt