GitHub Enterprise Server up to 3.0.18/3.1.10/3.2.2 Pages path traversal

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.
4.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in GitHub Enterprise Server up to 3.0.18/3.1.10/3.2.2. The affected element is an unknown function of the component Pages. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2021-22870. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitHub Enterprise Server up to 3.0.18/3.1.10/3.2.2 (Bug Tracking Software) and classified as problematic. This issue affects an unknown functionality of the component Pages. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-23. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. Impacted is confidentiality.

The weakness was disclosed 11/10/2021. It is possible to read the advisory at docs.github.com. The identification of this vulnerability is CVE-2021-22870 since 01/06/2021. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 3.0.19, 3.1.11, 3.2.3 or 3.3 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.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Path traversal
CWE: CWE-23 / CWE-22
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.19/3.1.11/3.2.3/3.3

Timelineinfo

01/06/2021 🔍
11/10/2021 +308 days 🔍
11/10/2021 +0 days 🔍
11/12/2021 +2 days 🔍

Sourcesinfo

Advisory: docs.github.com
Status: Confirmed

CVE: CVE-2021-22870 (🔍)
GCVE (CVE): GCVE-0-2021-22870
GCVE (VulDB): GCVE-100-186467

Entryinfo

Created: 11/10/2021 13:08
Updated: 11/12/2021 12:02
Changes: 11/10/2021 13:08 (41), 11/12/2021 12:02 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!