GitHub Enterprise Server 3.0.0/3.0.0.rc1/3.0.0.rc2 Fork improper authorization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.7$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in GitHub Enterprise Server 3.0.0/3.0.0.rc1/3.0.0.rc2. Impacted is an unknown function of the component Fork Handler. The manipulation results in improper authorization. This vulnerability is cataloged as CVE-2021-22862. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in GitHub Enterprise Server 3.0.0/3.0.0.rc1/3.0.0.rc2 (Bug Tracking Software). Affected is an unknown function of the component Fork Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 03/04/2021. The advisory is shared for download at docs.github.com. This vulnerability is traded as CVE-2021-22862. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1548.002.

Upgrading to version 3.0.1 eliminates this vulnerability. The upgrade is hosted for download at docs.github.com.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.9

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Improper authorization
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Enterprise Server 3.0.1

Timelineinfo

01/06/2021 🔍
03/04/2021 +57 days 🔍
03/04/2021 +0 days 🔍
03/14/2021 +10 days 🔍

Sourcesinfo

Advisory: docs.github.com
Status: Confirmed

CVE: CVE-2021-22862 (🔍)
GCVE (CVE): GCVE-0-2021-22862
GCVE (VulDB): GCVE-100-170604

Entryinfo

Created: 03/04/2021 06:32
Updated: 03/14/2021 12:57
Changes: 03/04/2021 06:32 (40), 03/06/2021 13:17 (5), 03/14/2021 12:57 (18)
Complete: 🔍
Cache ID: 216:0F8:103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!