CVE-2022-1935
First published: Mon Jun 06 2022(Updated: )
Incorrect authorization in GitLab EE affecting all versions from 12.0 before 14.9.5, all versions starting from 14.10 before 14.10.4, all versions starting from 15.0 before 15.0.1 allowed an attacker already in possession of a valid Project Trigger Token to misuse it from any location even when IP address restrictions were configured
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=12.0.0<14.9.5 | |
| GitLab | >=14.10.0<14.10.4 | |
| GitLab | =15.0.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-1935?
CVE-2022-1935 is considered a high severity vulnerability due to incorrect authorization allowing misuse of Project Trigger Tokens.
How do I fix CVE-2022-1935?
To fix CVE-2022-1935, upgrade GitLab to version 14.9.5 or later, or to version 14.10.4 or later, or to version 15.0.1 or later.
What versions are affected by CVE-2022-1935?
CVE-2022-1935 affects GitLab EE versions from 12.0 before 14.9.5, all versions from 14.10 before 14.10.4, and all versions from 15.0 before 15.0.1.
Who can exploit CVE-2022-1935?
An attacker already in possession of a valid Project Trigger Token can exploit CVE-2022-1935.
What are the potential impacts of CVE-2022-1935?
The potential impacts of CVE-2022-1935 include unauthorized access to project functionalities, leading to further exploitation.
- agent/references
- agent/type
- agent/weakness
- agent/author
- agent/remedy
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- 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.0.0
- version/gitlab/14.10.0
- version/gitlab/15.0.0