This is not the latest report. Click
here to view the latest report.
CWE Statistics for GitHub, Inc. as of 07/27/2023
0
40
40
13
Reference
0-69.9%
|
Provider |
32.5
Contributor
70-94.9%
Provider
95-100%
CVE | CNA Value | Alignment | NIST Value | Reason |
---|---|---|---|---|
CVE-2022-21680 (2 of 2) | CWE-1333 | CWE-1333 | ||
CWE-400 | More specific CWE option available | |||
CVE-2022-21681 (2 of 2) | CWE-1333 | CWE-1333 | ||
CWE-400 | More specific CWE option available | |||
CVE-2022-21684 (1 of 1) | CWE-287 | CWE-287 | ||
CVE-2022-21698 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-21707 (0 of 1) | CWE-863 | ≠ | CWE-862 | More specific CWE option available |
CVE-2022-21708 (0 of 1) | CWE-400 | ≠ | CWE-674 | More specific CWE option available |
CVE-2022-21713 (0 of 1) | CWE-863 | ≠ | CWE-639 | More specific CWE option available |
CVE-2022-21716 (0 of 1) | CWE-120 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-21718 (0 of 1) | CWE-668 | ≠ | CWE-862 | More specific CWE option available |
CVE-2022-23527 (1 of 1) | CWE-601 | CWE-601 | ||
CVE-2022-23640 (0 of 1) | CWE-611 | ≠ | CWE-776 | More specific CWE option available |
CVE-2022-31110 (0 of 1) | CWE-400 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-31112 (0 of 1) | CWE-200 | ≠ | CWE-212 | More specific CWE option available |
CVE-2022-31129 (0 of 1) | CWE-400 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-31139 (0 of 1) | CWE-200 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-31147 (1 of 1) | CWE-1333 | CWE-1333 | ||
CVE-2022-31156 (0 of 1) | CWE-829 | ≠ | CWE-347 | More specific CWE option available |
CVE-2022-31157 (0 of 1) | CWE-327 | ≠ | CWE-330 | More specific CWE option available |
CVE-2022-31158 (1 of 1) | CWE-294 | CWE-294 | ||
CVE-2022-31162 (2 of 2) | CWE-1258 | CWE-212 | ||
CWE-200 | More specific CWE option available | |||
CVE-2022-31173 (0 of 1) | CWE-400 | ≠ | CWE-674 | More specific CWE option available |
CVE-2022-31176 (0 of 1) | CWE-200 | ≠ | CWE-306 | More specific CWE option available |
CVE-2022-35915 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-35921 (0 of 1) | CWE-269 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-35922 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-35923 (0 of 1) | CWE-400 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-35925 (0 of 1) | CWE-287 | ≠ | CWE-307 | More specific CWE option available |
CVE-2022-36034 (2 of 2) | CWE-1333 | CWE-1333 | ||
CWE-400 | More specific CWE option available | |||
CVE-2022-36055 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-36064 (2 of 2) | CWE-1333 | CWE-1333 | ||
CWE-400 | More specific CWE option available | |||
CVE-2022-36065 (2 of 2) | CWE-22 | CWE-22 | ||
CWE-24 | CWE-22 | |||
CVE-2022-36074 (0 of 1) | CWE-200 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-36078 (1 of 1) | CWE-789 | CWE-1284 | ||
CVE-2022-36083 (0 of 1) | CWE-400 | ≠ | CWE-834 | More specific CWE option available |
CVE-2022-36086 (1 of 2) | CWE-119 | ≠ | CWE-1284 | More specific CWE option available |
CWE-787 | More specific CWE option available | |||
CVE-2022-36103 (0 of 1) | CWE-732 | ≠ | CWE-863 | More specific CWE option available |
CVE-2023-34451 (1 of 1) | CWE-401 | CWE-401 | ||
CVE-2023-35945 (0 of 1) | CWE-400 | ≠ | CWE-459 | More specific CWE option available |
CVE-2023-36466 (0 of 1) | CWE-20 | ≠ | CWE-287 | More specific CWE option available |
CVE-2023-36829 (2 of 2) | CWE-942 | CWE-697 | ||
CWE-863 | More specific CWE option available |