What is the severity of CVE-2022-1417?

CVE-2022-1417 has a medium severity rating due to improper access control vulnerabilities in GitLab.

How do I fix CVE-2022-1417?

To fix CVE-2022-1417, upgrade GitLab to version 14.8.6 or later, 14.9.4 or later, or 14.10.1 or later.

Who is affected by CVE-2022-1417?

CVE-2022-1417 affects all GitLab Community and Enterprise Editions starting from version 8.12 up to specific versions listed in the vulnerability report.

What does CVE-2022-1417 allow attackers to do?

CVE-2022-1417 allows non-project members to access the contents of Project Members-only Wikis through malicious continuous integration jobs.

When was CVE-2022-1417 identified?

CVE-2022-1417 was identified as a vulnerability in GitLab and needs to be addressed for the affected versions released before 14.10.1.

Vulnerability/
CVE-2022-1417

medium

4.3

CWE

863

10/5/2022

3/8/2024

CVE-2022-1417

First published: Tue May 10 2022(Updated: )

Improper access control in GitLab CE/EE affecting all versions starting from 8.12 before 14.8.6, all versions starting from 14.9 before 14.9.4, and all versions starting from 14.10 before 14.10.1 allows non-project members to access contents of Project Members-only Wikis via malicious CI jobs

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=8.12.0<14.8.6
GitLab	>=8.12.0<14.8.6
GitLab	>=14.9.0<14.9.4
GitLab	>=14.9.0<14.9.4
GitLab	=14.10.0
GitLab	=14.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1417?
CVE-2022-1417 has a medium severity rating due to improper access control vulnerabilities in GitLab.
How do I fix CVE-2022-1417?
To fix CVE-2022-1417, upgrade GitLab to version 14.8.6 or later, 14.9.4 or later, or 14.10.1 or later.
Who is affected by CVE-2022-1417?
CVE-2022-1417 affects all GitLab Community and Enterprise Editions starting from version 8.12 up to specific versions listed in the vulnerability report.
What does CVE-2022-1417 allow attackers to do?
CVE-2022-1417 allows non-project members to access the contents of Project Members-only Wikis through malicious continuous integration jobs.
When was CVE-2022-1417 identified?
CVE-2022-1417 was identified as a vulnerability in GitLab and needs to be addressed for the affected versions released before 14.10.1.

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/8.12.0
version/gitlab/14.9.0
version/gitlab/14.10.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-1417?
CVE-2022-1417 has a medium severity rating due to improper access control vulnerabilities in GitLab.
How do I fix CVE-2022-1417?
To fix CVE-2022-1417, upgrade GitLab to version 14.8.6 or later, 14.9.4 or later, or 14.10.1 or later.
Who is affected by CVE-2022-1417?
CVE-2022-1417 affects all GitLab Community and Enterprise Editions starting from version 8.12 up to specific versions listed in the vulnerability report.
What does CVE-2022-1417 allow attackers to do?
CVE-2022-1417 allows non-project members to access the contents of Project Members-only Wikis through malicious continuous integration jobs.
When was CVE-2022-1417 identified?
CVE-2022-1417 was identified as a vulnerability in GitLab and needs to be addressed for the affected versions released before 14.10.1.