CVE-2021-39869: Medium severity GitLab GitLab vulnerability
Published Oct 5, 2021
·Updated
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project.
Affected Software
6 affected components
GitLab GitLab>=8.9.0<14.1.7
GitLab GitLab>=8.9.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:30 PM
Data Sourced
via MITRE·12:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2021-39869?
CVE-2021-39869 has been classified as a medium severity vulnerability due to its potential to expose sensitive trigger tokens.
2
How do I fix CVE-2021-39869?
To fix CVE-2021-39869, upgrade to GitLab versions 14.2.6 or 14.1.8 or later.
3
Which versions of GitLab are affected by CVE-2021-39869?
CVE-2021-39869 affects all GitLab CE/EE versions from 8.9.0 to 14.1.7 and from 14.2.0 to 14.2.5.
4
What type of tokens are exposed by CVE-2021-39869?
CVE-2021-39869 exposes trigger tokens that are configured on the affected GitLab projects.
5
Is it safe to use versions prior to the patched update for CVE-2021-39869?
Using versions prior to the patched updates for CVE-2021-39869 is not safe due to the risk of exposing trigger tokens.