CVE-2020-26411: Medium severity gitlab vulnerability
Published Dec 11, 2020
·Updated
A potential DOS vulnerability was discovered in all versions of Gitlab starting from 13.4.x (>=13.4 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <13.6.2). Using a specific query name for a project search can cause statement timeouts that can lead to a potential DOS if abused.
Affected Software
3 affected components
GitLab GitLab>=13.4.0<13.4.7
GitLab GitLab>=13.5.0<13.5.5
GitLab GitLab>=13.6.0<13.6.2
Event History
Dec 11, 2020
CVE Published
via MITRE·04:09 AM
Data Sourced
via MITRE·04:09 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-26411?
CVE-2020-26411 is classified as a potential denial-of-service (DOS) vulnerability.
2
How do I fix CVE-2020-26411?
To remediate CVE-2020-26411, upgrade GitLab to versions 13.4.7, 13.5.5, or 13.6.2 or later.
3
What versions of GitLab are affected by CVE-2020-26411?
CVE-2020-26411 affects GitLab versions from 13.4.0 to 13.4.6, from 13.5.0 to 13.5.4, and from 13.6.0 to 13.6.1.
4
What triggers the DOS in CVE-2020-26411?
The DOS is triggered by using a specific project search query that can cause statement timeouts.
5
Is CVE-2020-26411 present in GitLab versions after 13.6.2?
CVE-2020-26411 is not present in GitLab versions published after 13.6.2.