GitLab Community Edition/Enterprise Edition up to 13.4.6/13.5.4/13.6.1 Project Search denial of service
|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.
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 13.4.6/13.5.4/13.6.1 (Bug Tracking Software). This affects an unknown code block of the component Project Search Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. This is going to have an impact on availability. The summary by CVE is:
A potential DOS vulnerability was discovered in all versions of Gitlab starting from 13.4.x (>=13.4 to =13.5 to =13.6 to
The weakness was disclosed 12/11/2020. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2020-26411 since 10/01/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 13.4.7, 13.5.5 or 13.6.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at gitlab.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB 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: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Denial of service
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 13.4.7/13.5.5/13.6.2
Timeline10/01/2020 CVE assigned
12/11/2020 +71 days Advisory disclosed
12/11/2020 +0 days VulDB entry created
12/15/2020 +4 days VulDB last update
CVE: CVE-2020-26411 (🔒)
EntryCreated: 12/11/2020 09:50 AM
Updated: 12/15/2020 08:41 PM
Changes: (1) source_cve_cna
Do you need the next level of professionalism?
Upgrade your account now!