What is the severity of CVE-2022-2228?

CVE-2022-2228 is classified as a high-severity vulnerability due to information exposure risks.

How do I fix CVE-2022-2228?

To remediate CVE-2022-2228, upgrade GitLab EE to version 14.10.5, 15.0.4, or 15.1.1 or later.

What types of systems are affected by CVE-2022-2228?

CVE-2022-2228 affects all versions of GitLab EE from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.

What does CVE-2022-2228 expose?

CVE-2022-2228 allows an attacker to obtain CI variables from a group using IP-based access restrictions.

Who can exploit CVE-2022-2228?

An attacker with the appropriate access tokens can exploit CVE-2022-2228.

Vulnerability/
CVE-2022-2228

medium

6.5

1/7/2022

3/8/2024

CVE-2022-2228

First published: Fri Jul 01 2022(Updated: )

Information exposure in GitLab EE affecting all versions from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker with the appropriate access tokens to obtain CI variables in a group with using IP-based access restrictions even if the GitLab Runner is calling from outside the allowed IP range

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.0.0<14.10.5
GitLab	>=15.0.0<15.0.4
GitLab	=15.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2228?
CVE-2022-2228 is classified as a high-severity vulnerability due to information exposure risks.
How do I fix CVE-2022-2228?
To remediate CVE-2022-2228, upgrade GitLab EE to version 14.10.5, 15.0.4, or 15.1.1 or later.
What types of systems are affected by CVE-2022-2228?
CVE-2022-2228 affects all versions of GitLab EE from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What does CVE-2022-2228 expose?
CVE-2022-2228 allows an attacker to obtain CI variables from a group using IP-based access restrictions.
Who can exploit CVE-2022-2228?
An attacker with the appropriate access tokens can exploit CVE-2022-2228.

agent/type
agent/references
agent/author
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/12.0.0
version/gitlab/15.0.0
version/gitlab/15.1.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-2228?
CVE-2022-2228 is classified as a high-severity vulnerability due to information exposure risks.
How do I fix CVE-2022-2228?
To remediate CVE-2022-2228, upgrade GitLab EE to version 14.10.5, 15.0.4, or 15.1.1 or later.
What types of systems are affected by CVE-2022-2228?
CVE-2022-2228 affects all versions of GitLab EE from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What does CVE-2022-2228 expose?
CVE-2022-2228 allows an attacker to obtain CI variables from a group using IP-based access restrictions.
Who can exploit CVE-2022-2228?
An attacker with the appropriate access tokens can exploit CVE-2022-2228.