2022 CVE Vulnerabilities
27,525 CVEs published in 2022.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2022-43830 | — | — | — | 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-43829 | — | — | — | 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-43828 | — | — | — | 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-43827 | — | — | — | 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-43826 | — | — | — | 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-43825 | — | — | — | 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-43824 | — | — | — | 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-43823 | — | — | — | 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-43822 | — | — | — | 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-43821 | — | — | — | 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-43820 | — | — | — | 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-43819 | — | — | — | 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-43818 | — | — | — | 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-43817 | — | — | — | 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-43816 | — | — | — | 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-43815 | — | — | — | 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-43814 | — | — | — | 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-43813 | — | — | — | 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-43812 | — | — | — | 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-43811 | — | — | — | 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-43810 | — | — | — | 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-43809 | — | — | — | 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-43808 | — | — | — | 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-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. |
Check if your code is affected by 2022 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now