This is not the latest report. Click
here to view the latest report.
CWE Statistics for GitHub, Inc. as of 12/09/2022
0
41
40
32
Reference
0-69.9%
|
Provider |
78.0
Contributor
70-94.9%
Provider
95-100%
CVE | CNA Value | Alignment | NIST Value | Reason |
---|---|---|---|---|
CVE-2020-11066 (0 of 1) | CWE-915 | ≠ | CWE-1321 | More specific CWE option available |
CVE-2021-32807 (0 of 1) | CWE-915 | ≠ | CWE-1321 | More specific CWE option available |
CVE-2021-32811 (0 of 1) | CWE-915 | ≠ | CWE-1321 | More specific CWE option available |
CVE-2022-23470 (1 of 1) | CWE-22 | CWE-22 | ||
CVE-2022-29187 (2 of 2) | CWE-427 | CWE-427 | ||
CWE-282 | More specific CWE option available | |||
CVE-2022-31001 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-31002 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-31003 (2 of 2) | CWE-122 | CWE-787 | ||
CWE-787 | CWE-787 | |||
CVE-2022-31031 (1 of 1) | CWE-120 | CWE-120 | ||
CVE-2022-31188 (1 of 1) | CWE-918 | CWE-918 | ||
CVE-2022-36033 (2 of 2) | CWE-79 | CWE-79 | ||
CWE-87 | CWE-79 | |||
CVE-2022-39250 (2 of 2) | CWE-287 | CWE-287 | ||
CWE-322 | More specific CWE option available | |||
CVE-2022-39251 (2 of 2) | CWE-287 | CWE-287 | ||
CWE-322 | More specific CWE option available | |||
CVE-2022-39261 (1 of 1) | CWE-22 | CWE-22 | ||
CVE-2022-39316 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-39317 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-39318 (2 of 2) | CWE-369 | CWE-369 | ||
CWE-20 | More specific CWE option available | |||
CVE-2022-39319 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-39320 (1 of 1) | CWE-125 | CWE-125 | ||
CVE-2022-39334 (1 of 1) | CWE-295 | CWE-295 | ||
CVE-2022-39339 (1 of 1) | CWE-319 | CWE-319 | ||
CVE-2022-39347 (1 of 1) | CWE-22 | CWE-22 | ||
CVE-2022-39368 (3 of 3) | CWE-404 | CWE-404 | ||
CWE-459 | CWE-404 | |||
CWE-459 | CWE-459 | |||
CVE-2022-39383 (1 of 1) | CWE-918 | CWE-918 | ||
CVE-2022-39395 (1 of 1) | CWE-269 | CWE-269 | ||
CVE-2022-41877 (0 of 1) | CWE-119 | ≠ | CWE-125 | More specific CWE option available |
CVE-2022-41885 (1 of 1) | CWE-131 | CWE-131 | ||
CVE-2022-41914 (0 of 1) | CWE-200 | ≠ | CWE-203 | More specific CWE option available |
CVE-2022-41916 (1 of 1) | CWE-193 | CWE-193 | ||
CVE-2022-41917 (1 of 1) | CWE-200 | CWE-200 | ||
CVE-2022-41918 (2 of 2) | CWE-863 | CWE-863 | ||
CWE-612 | More specific CWE option available | |||
CVE-2022-41921 (0 of 1) | CWE-20 | ≠ | CWE-770 | More specific CWE option available |
CVE-2022-41923 (1 of 1) | CWE-269 | CWE-269 | ||
CVE-2022-41924 (2 of 2) | CWE-352 | CWE-352 | ||
CWE-346 | More specific CWE option available | |||
CVE-2022-41945 (0 of 1) | CWE-94 | ≠ | CWE-77 | More specific CWE option available |
CVE-2022-41969 (0 of 1) | CWE-400 | ≠ | CWE-521 | Initial Weakness |
CVE-2022-41970 (2 of 2) | CWE-863 | CWE-863 | ||
CWE-284 | More specific CWE option available | |||
CVE-2022-41971 (2 of 2) | CWE-200 | CWE-668 | ||
CWE-359 | CWE-668 | |||
CVE-2022-46152 (1 of 1) | CWE-129 | CWE-129 | ||
CVE-2022-46169 (0 of 1) | CWE-74 | ≠ | CWE-77 | More specific CWE option available |