CVE-2021-22229
First published: Tue Jul 06 2021(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.8. Under a special condition it was possible to access data of an internal repository through project fork done by a project member.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=12.8<13.11.6 | |
| GitLab | >=13.12.0<13.12.6 | |
| GitLab | >=14.0.0<14.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-22229?
CVE-2021-22229 is classified as a medium severity vulnerability.
How do I fix CVE-2021-22229?
To fix CVE-2021-22229, upgrade your GitLab instance to a version greater than 13.11.6, 13.12.6 or 14.0.2.
Which versions of GitLab are affected by CVE-2021-22229?
CVE-2021-22229 affects all GitLab versions starting from 12.8 up to version 14.0.2.
What type of vulnerability is CVE-2021-22229?
CVE-2021-22229 is a data exposure vulnerability that allows access to internal repository data.
Can CVE-2021-22229 impact my GitLab project security?
Yes, CVE-2021-22229 can significantly impact your GitLab project security by potentially exposing sensitive internal repository data.
- agent/references
- agent/type
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/12.8
- version/gitlab/13.12.0
- version/gitlab/14.0.0