CVE-2021-39866: Medium severity GitLab GitLab vulnerability
Published Oct 5, 2021
·Updated
A business logic error in the project deletion process in GitLab 13.6 and later allows persistent access via project access tokens.
Affected Software
6 affected components
GitLab GitLab>=13.6.0<14.1.7
GitLab GitLab>=13.6.0<14.1.7
GitLab GitLab>=14.2.0<14.2.5
GitLab GitLab>=14.2.0<14.2.5
GitLab GitLab=4.3.0
GitLab GitLab=4.3.0
Event History
Oct 5, 2021
CVE Published
via MITRE·12:35 PM
Data Sourced
via MITRE·12:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2021-39866?
CVE-2021-39866 has been rated as a medium severity vulnerability.
2
How do I fix CVE-2021-39866?
To resolve CVE-2021-39866, upgrade GitLab to version 14.1.7 or later, or 14.2.5 or later.
3
Which versions of GitLab are affected by CVE-2021-39866?
CVE-2021-39866 affects GitLab versions from 13.6.0 to 14.1.6 and from 14.2.0 to 14.2.5.
4
What is the impact of CVE-2021-39866?
CVE-2021-39866 allows unauthorized persistent access via project access tokens due to a business logic error.
5
Is there a workaround for CVE-2021-39866 before upgrading?
There are no known effective workarounds for CVE-2021-39866, so upgrading is strongly recommended.