CVE-2021-39897: Medium severity gitlab vulnerability
Published Nov 4, 2021
·Updated
Improper access control in GitLab CE/EE version 10.5 and above allowed subgroup members with inherited access to a project from a parent group to still have access even after the subgroup is transferred
Affected Software
6 affected components
GitLab GitLab>=12.9.0<12.9.8
GitLab GitLab>=12.9.0<12.9.8
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab>=12.10.0<12.10.7
GitLab GitLab=13.0.0
GitLab GitLab=13.0.0
Event History
Nov 4, 2021
CVE Published
via MITRE·11:07 PM
Data Sourced
via MITRE·11:07 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2021-39897?
CVE-2021-39897 has been classified as a medium severity vulnerability due to improper access control.
2
How do I fix CVE-2021-39897?
To fix CVE-2021-39897, update GitLab to version 12.10.8 or later, or version 13.0.1 or later.
3
What versions of GitLab are affected by CVE-2021-39897?
CVE-2021-39897 affects GitLab CE/EE versions from 10.5 to 12.10.7.
4
What type of vulnerability is CVE-2021-39897?
CVE-2021-39897 is an improper access control vulnerability allowing unauthorized access to projects.
5
Can subgroup members retain access after transfer according to CVE-2021-39897?
Yes, subgroup members with inherited access can retain project access even after the subgroup is transferred.