What is the severity of CVE-2022-0152?

CVE-2022-0152 is rated as a critical vulnerability due to unauthorized access to sensitive fields in the GraphQL API.

How do I fix CVE-2022-0152?

To fix CVE-2022-0152, update GitLab to version 14.4.5 or later, or ensure you are using version 14.5.3 or later if on version 14.5.

Which versions of GitLab are affected by CVE-2022-0152?

CVE-2022-0152 affects GitLab versions from 13.10 to 14.4.5, from 14.5.0 to 14.5.3, and from 14.6.0 to 14.6.2.

What type of vulnerability is CVE-2022-0152?

CVE-2022-0152 is an unauthorized access vulnerability targeting the GraphQL API in GitLab.

What are the consequences of CVE-2022-0152?

Exploitation of CVE-2022-0152 can lead to unauthorized access to sensitive data through the GraphQL API.

Vulnerability/
CVE-2022-0152

medium

6.5

CWE

862

18/1/2022

2/8/2024

CVE-2022-0152

First published: Tue Jan 18 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 13.10 before 14.4.5, all versions starting from 14.5.0 before 14.5.3, all versions starting from 14.6.0 before 14.6.2. GitLab was vulnerable to unauthorized access to some particular fields through the GraphQL API.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.10<14.4.5
GitLab	>=13.10<14.4.5
GitLab	>=14.5.0<14.5.3
GitLab	>=14.5.0<14.5.3
GitLab	>=14.6.0<14.6.2
GitLab	>=14.6.0<14.6.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0152?
CVE-2022-0152 is rated as a critical vulnerability due to unauthorized access to sensitive fields in the GraphQL API.
How do I fix CVE-2022-0152?
To fix CVE-2022-0152, update GitLab to version 14.4.5 or later, or ensure you are using version 14.5.3 or later if on version 14.5.
Which versions of GitLab are affected by CVE-2022-0152?
CVE-2022-0152 affects GitLab versions from 13.10 to 14.4.5, from 14.5.0 to 14.5.3, and from 14.6.0 to 14.6.2.
What type of vulnerability is CVE-2022-0152?
CVE-2022-0152 is an unauthorized access vulnerability targeting the GraphQL API in GitLab.
What are the consequences of CVE-2022-0152?
Exploitation of CVE-2022-0152 can lead to unauthorized access to sensitive data through the GraphQL API.

agent/references
agent/type
agent/weakness
agent/author
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/13.10
version/gitlab/14.5.0
version/gitlab/14.6.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-0152?
CVE-2022-0152 is rated as a critical vulnerability due to unauthorized access to sensitive fields in the GraphQL API.
How do I fix CVE-2022-0152?
To fix CVE-2022-0152, update GitLab to version 14.4.5 or later, or ensure you are using version 14.5.3 or later if on version 14.5.
Which versions of GitLab are affected by CVE-2022-0152?
CVE-2022-0152 affects GitLab versions from 13.10 to 14.4.5, from 14.5.0 to 14.5.3, and from 14.6.0 to 14.6.2.
What type of vulnerability is CVE-2022-0152?
CVE-2022-0152 is an unauthorized access vulnerability targeting the GraphQL API in GitLab.
What are the consequences of CVE-2022-0152?
Exploitation of CVE-2022-0152 can lead to unauthorized access to sensitive data through the GraphQL API.