2022 CVE Vulnerabilities
27,563 CVEs published in 2022.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2022-43807 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43806 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43805 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43804 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43803 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43802 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43801 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43800 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43799 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43798 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43797 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43796 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43795 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43794 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43793 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43792 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43791 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43790 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43789 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43788 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43787 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43786 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43785 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43784 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2022-43783 | — | — | — | Jan 1, 2023 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
Check if your code is affected by 2022 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now