) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This is not the latest report. Click
here to view the latest report.
CWE Statistics for GitHub, Inc. as of 04/22/2022
0
43
40
27
Reference
0-69.9%
|
|
Contributor |
62.8
Contributor
70-94.9%
Provider
95-100%
| CVE | CNA Value | Alignment | NIST Value | Reason |
|---|---|---|---|---|
| CVE-2021-41119 (1 of 1) | CWE-400 | CWE-400 | ||
| CVE-2021-41233 (0 of 1) | CWE-862 | ≠ | CWE-863 | More specific CWE option available |
| CVE-2022-21706 (2 of 2) | CWE-863 | CWE-863 | ||
| CWE-284 | More specific CWE option available | |||
| CVE-2022-23607 (0 of 1) | CWE-200 | ≠ | CWE-601 | |
| CVE-2022-23625 (1 of 1) | CWE-755 | CWE-755 | ||
| CVE-2022-23640 (1 of 1) | CWE-611 | CWE-611 | ||
| CVE-2022-23648 (0 of 1) | CWE-200 | ≠ | CWE-287 | More specific CWE option available |
| CVE-2022-23650 (1 of 1) | CWE-321 | CWE-798 | ||
| CVE-2022-23656 (1 of 1) | CWE-79 | CWE-79 | ||
| CVE-2022-24711 (0 of 1) | CWE-20 | ≠ | CWE-94 | More specific CWE option available |
| CVE-2022-24716 (1 of 1) | CWE-22 | CWE-22 | ||
| CVE-2022-24719 (0 of 1) | CWE-359 | ≠ | CWE-601 | More specific CWE option available |
| CVE-2022-24720 (0 of 1) | CWE-20 | ≠ | CWE-78 | More specific CWE option available |
| CVE-2022-24722 (1 of 1) | CWE-79 | CWE-79 | ||
| CVE-2022-24726 (1 of 1) | CWE-400 | CWE-400 | ||
| CVE-2022-24730 (1 of 2) | CWE-22 | CWE-22 | ||
| CWE-284 | ≠ | CWE-209 | ||
| CVE-2022-24731 (1 of 2) | CWE-22 | CWE-22 | ||
| CWE-284 | ≠ | CWE-209 | More specific CWE option available | |
| CVE-2022-24734 (1 of 1) | CWE-94 | CWE-94 | ||
| CVE-2022-24738 (1 of 1) | CWE-287 | CWE-287 | ||
| CVE-2022-24740 (1 of 1) | CWE-287 | CWE-287 | ||
| CVE-2022-24743 (1 of 1) | CWE-613 | CWE-613 | ||
| CVE-2022-24749 (2 of 2) | CWE-80 | CWE-79 | ||
| CWE-434 | More specific CWE option available | |||
| CVE-2022-24754 (0 of 1) | CWE-120 | ≠ | CWE-787 | More specific CWE option available |
| CVE-2022-24760 (0 of 1) | CWE-74 | ≠ | CWE-1321 | More specific CWE option available |
| CVE-2022-24766 (1 of 1) | CWE-444 | CWE-444 | ||
| CVE-2022-24768 (0 of 1) | CWE-200 | ≠ | CWE-269 | More specific CWE option available |
| CVE-2022-24769 (1 of 1) | CWE-732 | CWE-732 | ||
| CVE-2022-24774 (2 of 2) | CWE-20 | CWE-20 | ||
| CWE-35 | CWE-22 | |||
| CVE-2022-24784 (0 of 1) | CWE-200 | ≠ | CWE-326 | More specific CWE option available |
| CVE-2022-24785 (2 of 2) | CWE-22 | CWE-22 | ||
| CWE-27 | CWE-22 | |||
| CVE-2022-24787 (1 of 1) | CWE-697 | CWE-697 | ||
| CVE-2022-24788 (1 of 1) | CWE-120 | CWE-119 | ||
| CVE-2022-24793 (1 of 1) | CWE-120 | CWE-120 | ||
| CVE-2022-24798 (1 of 1) | CWE-212 | CWE-212 | ||
| CVE-2022-24802 (0 of 1) | CWE-915 | ≠ | CWE-1321 | More specific CWE option available |
| CVE-2022-24804 (0 of 1) | CWE-200 | ≠ | CWE-276 | Initial Weakness |
| CVE-2022-24820 (1 of 1) | CWE-359 | CWE-200 | ||
| CVE-2022-24837 (0 of 1) | CWE-200 | ≠ | CWE-434 | Initial Weakness |
| CVE-2022-24838 (0 of 1) | CWE-74 | ≠ | CWE-77 | More specific CWE option available |
| CVE-2022-24843 (1 of 1) | CWE-22 | CWE-22 |