CVE-2021-22258: Medium severity gitlab vulnerability
Published Oct 5, 2021
·Updated
The project import/export feature in GitLab 8.9 and greater could be used to obtain otherwise private email addresses
Affected Software
6 affected components
GitLab GitLab>=8.9.0<14.0.9
GitLab GitLab>=8.9.0<14.0.9
GitLab GitLab>=14.1.0<14.1.4
GitLab GitLab>=14.1.0<14.1.4
GitLab GitLab>=14.2.0<14.2.2
GitLab GitLab>=14.2.0<14.2.2
Event History
Oct 5, 2021
CVE Published
via MITRE·01:49 PM
Data Sourced
via MITRE·01:49 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2021-22258?
CVE-2021-22258 is classified as a high severity vulnerability due to its potential to expose private email addresses.
2
How do I fix CVE-2021-22258?
To fix CVE-2021-22258, upgrade your GitLab instance to version 14.0.9 or later, or the relevant patched versions.
3
Which versions of GitLab are affected by CVE-2021-22258?
CVE-2021-22258 affects GitLab versions from 8.9.0 up to, but not including, 14.0.9, as well as 14.1.0 to 14.1.4 and 14.2.0 to 14.2.2.
4
What data is at risk due to CVE-2021-22258?
CVE-2021-22258 could allow unauthorized access to private email addresses associated with projects in GitLab.
5
Is there a workaround for CVE-2021-22258 if I can't upgrade?
There are no known workarounds for CVE-2021-22258, so upgrading to a safe version is the recommended action.