GitHub Enterprise Server up to 3.0.0 REST API improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in GitHub Enterprise Server up to 2.4.20/2.20.23/2.21.14/2.22.6/3.0.0. This issue affects some unknown processing of the component REST API. The manipulation leads to improper authorization. This vulnerability is listed as CVE-2021-22861. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in GitHub Enterprise Server up to 2.4.20/2.20.23/2.21.14/2.22.6/3.0.0 (Bug Tracking Software). It has been rated as critical. This issue affects some unknown processing of the component REST API. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability.
The weakness was presented 03/04/2021. It is possible to read the advisory at docs.github.com. The identification of this vulnerability is CVE-2021-22861. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.
Upgrading to version 2.4.21, 2.20.24, 2.21.15, 2.22.7 or 3.0.1 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.4.0
- 2.4.1
- 2.4.2
- 2.4.3
- 2.4.4
- 2.4.5
- 2.4.6
- 2.4.7
- 2.4.8
- 2.4.9
- 2.4.10
- 2.4.11
- 2.4.12
- 2.4.13
- 2.4.14
- 2.4.15
- 2.4.16
- 2.4.17
- 2.4.18
- 2.4.19
- 2.4.20
- 2.20.0
- 2.20.1
- 2.20.2
- 2.20.3
- 2.20.4
- 2.20.5
- 2.20.6
- 2.20.7
- 2.20.8
- 2.20.9
- 2.20.10
- 2.20.11
- 2.20.12
- 2.20.13
- 2.20.14
- 2.20.15
- 2.20.16
- 2.20.17
- 2.20.18
- 2.20.19
- 2.20.20
- 2.20.21
- 2.20.22
- 2.20.23
- 2.21.0
- 2.21.1
- 2.21.2
- 2.21.3
- 2.21.4
- 2.21.5
- 2.21.6
- 2.21.7
- 2.21.8
- 2.21.9
- 2.21.10
- 2.21.11
- 2.21.12
- 2.21.13
- 2.21.14
- 2.22.0
- 2.22.1
- 2.22.2
- 2.22.3
- 2.22.4
- 2.22.5
- 2.22.6
- 3.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Enterprise Server 2.4.21/2.20.24/2.21.15/2.22.7/3.0.1
Timeline
01/06/2021 🔍03/04/2021 🔍
03/04/2021 🔍
03/14/2021 🔍
Sources
Advisory: docs.github.comStatus: Confirmed
CVE: CVE-2021-22861 (🔍)
GCVE (CVE): GCVE-0-2021-22861
GCVE (VulDB): GCVE-100-170603
Entry
Created: 03/04/2021 06:31Updated: 03/14/2021 12:51
Changes: 03/04/2021 06:31 (40), 03/06/2021 13:11 (5), 03/14/2021 12:51 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.