CVE-2021-22239: Medium severity gitlab vulnerability
Published Sep 9, 2021
·Updated
An unauthorized user was able to insert metadata when creating new issue on GitLab CE/EE 14.0 and later.
Affected Software
4 affected components
GitLab GitLab>=14.0.0<14.0.7
GitLab GitLab>=14.0.0<14.0.7
GitLab GitLab>=14.1.0<14.1.2
GitLab GitLab>=14.1.0<14.1.2
Event History
Sep 9, 2021
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2021-22239?
The severity of CVE-2021-22239 is classified as a high-risk vulnerability due to the potential for unauthorized access.
2
How do I fix CVE-2021-22239?
To fix CVE-2021-22239, upgrade to GitLab version 14.0.8 or later for both Community and Enterprise editions.
3
What kind of impact does CVE-2021-22239 have on GitLab?
CVE-2021-22239 allows unauthorized users to insert malicious metadata when creating new issues, which could lead to further exploitation.
4
Which versions of GitLab are affected by CVE-2021-22239?
CVE-2021-22239 affects GitLab versions 14.0.0 through 14.1.2 for both Community and Enterprise editions.
5
Is CVE-2021-22239 present in older versions of GitLab?
CVE-2021-22239 is not present in versions prior to 14.0.0 of GitLab.