CVE-2021-39889: Medium severity GitLab GitLab vulnerability
Published Oct 5, 2021
·Updated
In all versions of GitLab EE since version 14.1, due to an insecure direct object reference vulnerability, an endpoint may reveal the protected branch name to a malicious user who makes a crafted API call with the ID of the protected branch.
Affected Software
3 affected components
GitLab GitLab>=14.1.0<14.1.7
GitLab GitLab>=14.2.0<14.2.5
GitLab GitLab>=14.3.0<14.3.1
Event History
Oct 5, 2021
CVE Published
via MITRE·01:43 PM
Data Sourced
via MITRE·01:43 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2021-39889?
CVE-2021-39889 has been classified as a medium severity vulnerability.
2
How do I fix CVE-2021-39889?
To mitigate CVE-2021-39889, upgrade to GitLab EE version 14.1.7, 14.2.6, or 14.3.2 or later.
3
What impact does CVE-2021-39889 have on GitLab EE users?
CVE-2021-39889 could allow unauthorized users to discover the names of protected branches through crafted API calls.
4
Which versions of GitLab EE are affected by CVE-2021-39889?
CVE-2021-39889 affects GitLab EE versions 14.1.0 to 14.1.6, 14.2.0 to 14.2.5, and 14.3.0 to 14.3.1.
5
Who is at risk due to CVE-2021-39889?
Users of GitLab EE versions listed in the vulnerability's range are at risk of exposing protected branch names to malicious actors.