What is the severity of CVE-2022-1936?

CVE-2022-1936 is considered a high severity vulnerability due to its potential to allow unauthorized access to sensitive project data.

How do I fix CVE-2022-1936?

To mitigate CVE-2022-1936, update GitLab to version 14.9.5 or higher, or to any version within the 14.10.x or 15.0.x series that is not affected.

Who is affected by CVE-2022-1936?

CVE-2022-1936 affects GitLab EE users on versions from 12.0 before 14.9.5, from 14.10 before 14.10.4, and 15.0 before 15.0.1.

What type of vulnerability is CVE-2022-1936?

CVE-2022-1936 is classified as an authorization vulnerability that can be exploited to misuse Project Deploy Tokens.

Can I check the status of CVE-2022-1936 fixes in my environment?

Yes, you can check your GitLab version against the fixed versions mentioned in the CVE description to ensure you are not vulnerable.

Vulnerability/
CVE-2022-1936

medium

6.5

CWE

863

6/6/2022

3/8/2024

CVE-2022-1936

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 Deploy 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-1936.json

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1936?
CVE-2022-1936 is considered a high severity vulnerability due to its potential to allow unauthorized access to sensitive project data.
How do I fix CVE-2022-1936?
To mitigate CVE-2022-1936, update GitLab to version 14.9.5 or higher, or to any version within the 14.10.x or 15.0.x series that is not affected.
Who is affected by CVE-2022-1936?
CVE-2022-1936 affects GitLab EE users on versions from 12.0 before 14.9.5, from 14.10 before 14.10.4, and 15.0 before 15.0.1.
What type of vulnerability is CVE-2022-1936?
CVE-2022-1936 is classified as an authorization vulnerability that can be exploited to misuse Project Deploy Tokens.
Can I check the status of CVE-2022-1936 fixes in my environment?
Yes, you can check your GitLab version against the fixed versions mentioned in the CVE description to ensure you are not vulnerable.

agent/references
agent/type
agent/author
agent/remedy
agent/weakness
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.