CVE-2022-0090
First published: Tue Jan 18 2022(Updated: )
An issue has been discovered affecting GitLab versions prior to 14.4.5, between 14.5.0 and 14.5.3, and between 14.6.0 and 14.6.1. GitLab is configured in a way that it doesn't ignore replacement references with git sub-commands, allowing a malicious user to spoof the contents of their commits in the UI.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <14.4.5 | |
| GitLab | <14.4.5 | |
| GitLab | >=14.5.0<14.5.3 | |
| GitLab | >=14.5.0<14.5.3 | |
| GitLab | >=14.6.0<14.6.1 | |
| GitLab | >=14.6.0<14.6.1 |
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-2022-0090?
CVE-2022-0090 is considered a medium severity vulnerability.
How do I fix CVE-2022-0090?
To fix CVE-2022-0090, you should upgrade GitLab to version 14.4.5 or later.
What versions of GitLab are affected by CVE-2022-0090?
CVE-2022-0090 affects GitLab versions prior to 14.4.5, between 14.5.0 and 14.5.3, and between 14.6.0 and 14.6.1.
What kind of attack does CVE-2022-0090 enable?
CVE-2022-0090 allows a malicious user to spoof the contents of their commits in GitLab.
Is GitLab Community Edition affected by CVE-2022-0090?
Yes, both GitLab Community Edition and Enterprise Edition are affected by CVE-2022-0090.
- agent/type
- agent/references
- agent/author
- agent/weakness
- 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/14.5.0
- version/gitlab/14.6.0