CVE-2021-39889
First published: Tue Oct 05 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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=14.1.0<14.1.7 | |
| GitLab | >=14.2.0<14.2.5 | |
| GitLab | >=14.3.0<14.3.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-39889?
CVE-2021-39889 has been classified as a medium severity vulnerability.
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.
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.
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.
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.
- agent/type
- agent/references
- agent/author
- agent/weakness
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/14.1.0
- version/gitlab/14.2.0
- version/gitlab/14.3.0