This is not the latest report. Click
here to view the latest report.
CWE Statistics for GitHub, Inc. as of 07/22/2023
0
42
40
10
Reference
0-69.9%
|
Provider |
23.8
Contributor
70-94.9%
Provider
95-100%
CVE | CNA Value | Alignment | NIST Value | Reason |
---|---|---|---|---|
CVE-2021-43838 (0 of 1) | CWE-400 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-23527 (1 of 1) | CWE-601 | CWE-601 | ||
CVE-2022-23633 (0 of 1) | CWE-200 | ≠ | CWE-212 | More specific CWE option available |
CVE-2022-23635 (0 of 1) | CWE-287 | ≠ | CWE-1284 | More specific CWE option available |
CVE-2022-29160 (0 of 1) | CWE-284 | ≠ | CWE-459 | More specific CWE option available |
CVE-2022-29161 (0 of 1) | CWE-327 | ≠ | CWE-326 | More specific CWE option available |
CVE-2022-29167 (0 of 1) | CWE-400 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-29169 (0 of 1) | CWE-20 | ≠ | CWE-1333 | More specific CWE option available |
CVE-2022-29171 (0 of 1) | CWE-74 | ≠ | CWE-94 | More specific CWE option available |
CVE-2022-29196 (0 of 1) | CWE-20 | ≠ | CWE-1284 | More specific CWE option available |
CVE-2022-29200 (0 of 1) | CWE-20 | ≠ | CWE-1284 | More specific CWE option available |
CVE-2022-29202 (1 of 2) | CWE-20 | ≠ | CWE-1284 | More specific CWE option available |
CWE-400 | More specific CWE option available | |||
CVE-2022-29213 (0 of 1) | CWE-20 | ≠ | CWE-617 | More specific CWE option available |
CVE-2022-29228 (0 of 1) | CWE-617 | ≠ | CWE-416 | More specific CWE option available |
CVE-2022-29248 (0 of 1) | CWE-200 | ≠ | CWE-565 | More specific CWE option available |
CVE-2022-29249 (3 of 3) | CWE-328 | CWE-326 | ||
CWE-328 | CWE-327 | |||
CWE-327 | CWE-327 | |||
CVE-2022-31008 (0 of 1) | CWE-330 | ≠ | CWE-335 | More specific CWE option available |
CVE-2022-31016 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-31034 (0 of 2) | CWE-330 | ≠ | CWE-331 | More specific CWE option available |
≠ | CWE-335 | |||
CVE-2022-31078 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-31079 (0 of 1) | CWE-400 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-31108 (0 of 1) | CWE-74 | ≠ | CWE-79 | 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-34457 (1 of 1) | CWE-20 | CWE-20 | ||
CVE-2023-35934 (0 of 1) | CWE-200 | ≠ | CWE-601 | More specific CWE option available |
CVE-2023-36829 (2 of 2) | CWE-942 | CWE-697 | ||
CWE-863 | More specific CWE option available |