GitLab Community Edition/Enterprise Edition up to 13.0.1 Email Verification privileges management
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in GitLab Community Edition and Enterprise Edition up to 13.0.1. This vulnerability affects unknown code of the component Email Verification. The manipulation leads to privileges management. This vulnerability was named CVE-2020-13265. The attack can be initiated remotely. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as critical has been found in GitLab Community Edition and Enterprise Edition up to 13.0.1 (Bug Tracking Software). This affects an unknown function of the component Email Verification. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
User email verification bypass in GitLab CE/EE 12.5 and later through 13.0.1 allows user to bypass email verification
The weakness was shared 06/19/2020 (Website). It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2020-13265 since 05/21/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-157062, VDB-157061, VDB-157060 and VDB-157058 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/21/2020 🔍06/19/2020 🔍
06/21/2020 🔍
10/26/2020 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-13265 (🔍)
GCVE (CVE): GCVE-0-2020-13265
GCVE (VulDB): GCVE-100-157059
See also: 🔍
Entry
Created: 06/21/2020 09:38Updated: 10/26/2020 08:50
Changes: 06/21/2020 09:38 (38), 06/21/2020 09:43 (12), 10/26/2020 08:46 (1), 10/26/2020 08:50 (1)
Complete: 🔍
Cache ID: 216:F21:103
No comments yet. Languages: en.
Please log in to comment.