CVE-2022-3820
First published: Tue Jan 24 2023(Updated: )
An issue has been discovered in GitLab affecting all versions starting from 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2. GitLab was not performing correct authentication with some Package Registries when IP address restrictions were configured, allowing an attacker already in possession of a valid Deploy Token to misuse it from any location.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=15.4.0<15.4.6 | |
| GitLab | >=15.4.0<15.4.6 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | =15.6.0 | |
| GitLab | =15.6.0 |
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 CVE-2022-3820?
CVE-2022-3820 is an issue in GitLab that affects all versions starting from 15.4 prior to 15.4.4 and 15.5 prior to 15.5.2.
What is the severity of CVE-2022-3820?
The severity of CVE-2022-3820 is medium with a severity value of 6.5.
How does CVE-2022-3820 affect GitLab?
CVE-2022-3820 in GitLab allows an attacker in possession of a valid token to bypass IP address restrictions configured for Package Registries.
Which versions of GitLab are affected by CVE-2022-3820?
Versions starting from 15.4 prior to 15.4.4 and 15.5 prior to 15.5.2 of GitLab are affected.
How can I fix CVE-2022-3820 in GitLab?
To fix CVE-2022-3820 in GitLab, you should update to version 15.4.4 or 15.5.2 or later.
- 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/15.4.0
- version/gitlab/15.5.0
- version/gitlab/15.6.0