Total
276812 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-42437 | 2024-02-14 | N/A | ||
| This is unused. | ||||
| CVE-2023-39450 | 2024-02-14 | N/A | ||
| This is unused. | ||||
| CVE-2023-38262 | 2024-02-14 | N/A | ||
| This is unused. | ||||
| CVE-2023-38137 | 2024-02-14 | N/A | ||
| This is unused. | ||||
| CVE-2024-0584 | 2024-02-14 | 0.0 Low | ||
| Do not use this CVE as it is duplicate of CVE-2023-6932 | ||||
| CVE-2023-42915 | 2024-02-14 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||||
| CVE-2024-0707 | 2024-02-13 | N/A | ||
| **REJECT** Not a valid vulnerability. | ||||
| CVE-2023-20576 | 2024-02-13 | 7.7 High | ||
| A vulnerability was found in AMD hardware due to insufficient verification of data authenticity in AGESA. This issue may allow a local unauthenticated attacker to update SPI ROM data, potentially resulting in denial of service or privilege escalation. | ||||
| CVE-2023-20577 | 2024-02-13 | 7.4 High | ||
| A vulnerability was found in AMD hardware due to a heap overflow in the SMM module. This issue could allow a local unauthenticated attacker to enable writing to SPI flash to execute arbitrary code. | ||||
| CVE-2024-1420 | 2024-02-12 | N/A | ||
| **REJECT** This is a duplicate of CVE-2024-1049. Please use CVE-2024-1049 instead. | ||||
| CVE-2023-6716 | 2024-02-09 | N/A | ||
| ** REJECT ** DO NOT USE THIS CVE RECORD. All references and descriptions in this record have been removed to prevent accidental usage. | ||||
| CVE-2022-0931 | 2024-02-08 | 0.0 Low | ||
| Red Hat Product Security does not consider this to be a vulnerability. Upstream has not acknowledged this issue as a security flaw. | ||||
| CVE-2024-22984 | 2024-02-07 | N/A | ||
| DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2023-5584 | 2024-02-06 | N/A | ||
| We have rejected this CVE as it was determined a non-security issue by the vendor. | ||||
| CVE-2023-47170 | 2024-02-05 | N/A | ||
| This candidate was in a CNA pool that was not assigned to any issues during 2023. | ||||
| CVE-2024-25001 | 2024-02-02 | N/A | ||
| ** REJECT ** DO NOT USE THIS CVE ID. ConsultIDs: none. Reason: This CVE ID is unused by its CNA. Notes: none. | ||||
| CVE-2024-0704 | 2024-02-01 | N/A | ||
| very low impact - impractical to correct | ||||
| CVE-2024-1087 | 2024-01-31 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is a duplicate of CVE-2024-1085. | ||||
| CVE-2023-3934 | 2024-01-31 | N/A | ||
| Please discard this CVE, we are not using this anymore. The vulnerability turned out to be a non-security issue | ||||
| CVE-2023-45930 | 2024-01-30 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||