CVE-2022-1983
First published: Fri Jul 01 2022(Updated: )
Incorrect authorization in GitLab EE affecting all versions from 10.7 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allowed an attacker already in possession of a valid Deploy Key or a Deploy Token to misuse it from any location to access Container Registries even when IP address restrictions were configured.
Credit: cve@gitlab.com cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.7.0<14.10.5 | |
| GitLab | >=15.0.0<15.0.4 | |
| GitLab | =15.1.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 the severity of CVE-2022-1983?
CVE-2022-1983 is classified as a high severity vulnerability due to incorrect authorization in GitLab EE.
How do I fix CVE-2022-1983?
To remediate CVE-2022-1983, upgrade GitLab EE to version 14.10.5, 15.0.4, or 15.1.1 or later.
What versions are affected by CVE-2022-1983?
CVE-2022-1983 affects all GitLab EE versions from 10.7 before 14.10.5, 15.0 before 15.0.4, and 15.1 before 15.1.1.
Who can exploit CVE-2022-1983?
An attacker with a valid Deploy Key or Deploy Token can exploit CVE-2022-1983 to gain unauthorized access to Container Registries.
What kind of access does CVE-2022-1983 permit?
CVE-2022-1983 allows unauthorized access to Container Registries from any location, bypassing IP address restrictions.
- agent/references
- agent/author
- agent/type
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/first-publish-date
- agent/event
- agent/source
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/tags
- agent/softwarecombine
- vendor/gitlab
- canonical/gitlab
- version/gitlab/10.7.0
- version/gitlab/15.0.0
- version/gitlab/15.1.0