Total
275807 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2023-5647 | 2024-01-23 | N/A | ||
** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-5212. Reason: This record is a reservation duplicate of CVE-2023-5212. Notes: All CVE users should reference CVE-2023-5212 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. | ||||
CVE-2023-5646 | 2024-01-23 | N/A | ||
** REJECT **DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-5241. Reason: This record is a reservation duplicate of CVE-2023-5241. Notes: All CVE users should reference CVE-2023-5241 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. | ||||
CVE-2024-23854 | 2024-01-23 | N/A | ||
This CVE ID was unused by the CNA. | ||||
CVE-2021-3533 | 2024-01-23 | N/A | ||
This vulnerability does not meet the criteria for a security vulnerability | ||||
CVE-2022-45795 | 2024-01-22 | N/A | ||
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||||
CVE-2022-45791 | 2024-01-22 | N/A | ||
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | ||||
CVE-2024-0706 | 2024-01-22 | N/A | ||
***REJECT*** This was a false positive report. | ||||
CVE-2024-0663 | 2024-01-19 | N/A | ||
REJECT: This is a false positive report. | ||||
CVE-2023-45485 | 2024-01-19 | 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-43956 | 2024-01-19 | N/A | ||
DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-36263. Reason: This record is a duplicate of CVE-2023-36263. Notes: All CVE users should reference CVE-2023-36263 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. | ||||
CVE-2023-47008 | 2024-01-19 | 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-47007 | 2024-01-19 | 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-47006 | 2024-01-19 | 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-47005 | 2024-01-19 | 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-47092 | 2024-01-18 | 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-2024-0694 | 2024-01-18 | N/A | ||
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-6620. Reason: This candidate is a reservation duplicate of CVE-2023-6620. Notes: All CVE users should reference CVE-2023-6620 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | ||||
CVE-2023-51381 | 2024-01-17 | N/A | ||
This CVE ID has been rejected or withdrawn by GitHub. | ||||
CVE-2023-22525 | 2024-01-16 | N/A | ||
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | ||||
CVE-2023-22520 | 2024-01-16 | N/A | ||
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. | ||||
CVE-2023-22514 | 2024-01-16 | N/A | ||
To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |