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.

Vulnerability/
CVE-2022-1935

medium

6.5

CWE

863

6/6/2022

3/8/2024

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

Remedy

https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1935.json

Never miss a vulnerability like this again

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

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.