What is the severity of CVE-2021-22228?

CVE-2021-22228 is classified as a moderate severity vulnerability due to improper access control allowing unauthorized access to project details.

How do I fix CVE-2021-22228?

To fix CVE-2021-22228, upgrade GitLab to version 13.11.6, 13.12.6, or 14.0.2 or later.

What systems are affected by CVE-2021-22228?

CVE-2021-22228 affects all versions of GitLab before 13.11.6, from 13.12 to before 13.12.6, and from 14.0 to before 14.0.2.

What types of access does CVE-2021-22228 allow unauthorized users?

CVE-2021-22228 allows unauthorized users to access sensitive project details via GraphQL.

Is there a workaround for CVE-2021-22228?

There is no known effective workaround for CVE-2021-22228 other than upgrading to a secure version.

Vulnerability/
CVE-2021-22228

medium

6.5

6/7/2021

3/8/2024

CVE-2021-22228

First published: Tue Jul 06 2021(Updated: )

An issue has been discovered in GitLab affecting all versions before 13.11.6, all versions starting from 13.12 before 13.12.6, and all versions starting from 14.0 before 14.0.2. Improper access control allows unauthorised users to access project details using Graphql.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<13.11.6
GitLab	>=13.12.0<13.12.6
GitLab	>=14.0.0<14.0.2

Remedy

https://gitlab.com/gitlab-org/gitlab/-/issues/332605

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22228?
CVE-2021-22228 is classified as a moderate severity vulnerability due to improper access control allowing unauthorized access to project details.
How do I fix CVE-2021-22228?
To fix CVE-2021-22228, upgrade GitLab to version 13.11.6, 13.12.6, or 14.0.2 or later.
What systems are affected by CVE-2021-22228?
CVE-2021-22228 affects all versions of GitLab before 13.11.6, from 13.12 to before 13.12.6, and from 14.0 to before 14.0.2.
What types of access does CVE-2021-22228 allow unauthorized users?
CVE-2021-22228 allows unauthorized users to access sensitive project details via GraphQL.
Is there a workaround for CVE-2021-22228?
There is no known effective workaround for CVE-2021-22228 other than upgrading to a secure version.

agent/type
agent/references
agent/author
agent/remedy
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
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.12.0
version/gitlab/14.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-2021-22228?
CVE-2021-22228 is classified as a moderate severity vulnerability due to improper access control allowing unauthorized access to project details.
How do I fix CVE-2021-22228?
To fix CVE-2021-22228, upgrade GitLab to version 13.11.6, 13.12.6, or 14.0.2 or later.
What systems are affected by CVE-2021-22228?
CVE-2021-22228 affects all versions of GitLab before 13.11.6, from 13.12 to before 13.12.6, and from 14.0 to before 14.0.2.
What types of access does CVE-2021-22228 allow unauthorized users?
CVE-2021-22228 allows unauthorized users to access sensitive project details via GraphQL.
Is there a workaround for CVE-2021-22228?
There is no known effective workaround for CVE-2021-22228 other than upgrading to a secure version.