GitLab Community Edition/Enterprise Edition 14.1 Password Expiration access control

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

Summaryinfo

A vulnerability, which was classified as critical, has been found in GitLab Community Edition and Enterprise Edition 14.1. Affected by this issue is some unknown functionality of the component Password Expiration Handler. This manipulation causes access control. This vulnerability is tracked as CVE-2021-39872. 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 GitLab Community Edition and Enterprise Edition 14.1 (Bug Tracking Software). It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Password Expiration Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality.

The weakness was disclosed 10/06/2021 as 33795. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2021-39872 since 08/23/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 14.1.7, 14.2.5 or 14.3.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (GitLab Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Access control
CWE: CWE-284 / 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: Community Edition/Enterprise Edition 14.1.7/14.2.5/14.3.1

Timelineinfo

08/23/2021 🔍
10/06/2021 +44 days 🔍
10/06/2021 +0 days 🔍
10/09/2021 +3 days 🔍

Sourcesinfo

Vendor: gitlab.com

Advisory: 33795
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-39872 (🔍)
GCVE (CVE): GCVE-0-2021-39872
GCVE (VulDB): GCVE-100-183877

Entryinfo

Created: 10/06/2021 09:01
Updated: 10/09/2021 11:53
Changes: 10/06/2021 09:01 (52), 10/06/2021 09:41 (2), 10/09/2021 11:53 (1)
Complete: 🔍
Committer: roga
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!