What is the severity of CVE-2022-2227?

CVE-2022-2227 has a medium severity due to improper access control vulnerabilities.

How do I fix CVE-2022-2227?

To fix CVE-2022-2227, upgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later.

Who is affected by CVE-2022-2227?

CVE-2022-2227 affects all versions of GitLab prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.

What types of information can be accessed due to CVE-2022-2227?

Due to CVE-2022-2227, unauthorized users can access job and project metadata.

What software versions should be updated to address CVE-2022-2227?

Update GitLab community and enterprise versions to 14.10.5, 15.0.4, or 15.1.1 to address CVE-2022-2227.

Vulnerability/
CVE-2022-2227

medium

4.3

CWE

732

1/7/2022

3/8/2024

CVE-2022-2227

First published: Fri Jul 01 2022(Updated: )

Improper access control in the runner jobs API in GitLab CE/EE affecting all versions prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows a previous maintainer of a project with a specific runner to access job and project meta data under certain conditions

Credit: cve@gitlab.com

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2227?
CVE-2022-2227 has a medium severity due to improper access control vulnerabilities.
How do I fix CVE-2022-2227?
To fix CVE-2022-2227, upgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later.
Who is affected by CVE-2022-2227?
CVE-2022-2227 affects all versions of GitLab prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What types of information can be accessed due to CVE-2022-2227?
Due to CVE-2022-2227, unauthorized users can access job and project metadata.
What software versions should be updated to address CVE-2022-2227?
Update GitLab community and enterprise versions to 14.10.5, 15.0.4, or 15.1.1 to address CVE-2022-2227.

agent/type
agent/references
agent/weakness
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/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-2227?
CVE-2022-2227 has a medium severity due to improper access control vulnerabilities.
How do I fix CVE-2022-2227?
To fix CVE-2022-2227, upgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later.
Who is affected by CVE-2022-2227?
CVE-2022-2227 affects all versions of GitLab prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What types of information can be accessed due to CVE-2022-2227?
Due to CVE-2022-2227, unauthorized users can access job and project metadata.
What software versions should be updated to address CVE-2022-2227?
Update GitLab community and enterprise versions to 14.10.5, 15.0.4, or 15.1.1 to address CVE-2022-2227.