What is the severity of CVE-2022-0735?

CVE-2022-0735 has a high severity level due to the potential for unauthorized access to sensitive runner registration tokens.

How do I fix CVE-2022-0735?

To fix CVE-2022-0735, update GitLab to version 14.6.5 or later, version 14.7.4 or later, or version 14.8.2 or later.

Which versions are affected by CVE-2022-0735?

CVE-2022-0735 affects GitLab versions from 12.10 to 14.6.5, 14.7 to 14.7.4, and 14.8 to 14.8.2.

What type of vulnerability is CVE-2022-0735?

CVE-2022-0735 is an information disclosure vulnerability that allows unauthorized users to access sensitive tokens.

Is GitLab CE affected by CVE-2022-0735?

Yes, both GitLab CE and GitLab EE are affected by CVE-2022-0735 across specific version ranges.

Vulnerability/
CVE-2022-0735

critical

28/3/2022

2/8/2024

CVE-2022-0735

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions starting from 14.7 before 14.7.4, all versions starting from 14.8 before 14.8.2. An unauthorised user was able to steal runner registration tokens through an information disclosure vulnerability using quick actions commands.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.0<14.6.5
GitLab	>=12.0<14.6.5
GitLab	>=14.7<14.7.4
GitLab	>=14.7<14.7.4
GitLab	>=14.8<14.8.2
GitLab	>=14.8<14.8.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0735?
CVE-2022-0735 has a high severity level due to the potential for unauthorized access to sensitive runner registration tokens.
How do I fix CVE-2022-0735?
To fix CVE-2022-0735, update GitLab to version 14.6.5 or later, version 14.7.4 or later, or version 14.8.2 or later.
Which versions are affected by CVE-2022-0735?
CVE-2022-0735 affects GitLab versions from 12.10 to 14.6.5, 14.7 to 14.7.4, and 14.8 to 14.8.2.
What type of vulnerability is CVE-2022-0735?
CVE-2022-0735 is an information disclosure vulnerability that allows unauthorized users to access sensitive tokens.
Is GitLab CE affected by CVE-2022-0735?
Yes, both GitLab CE and GitLab EE are affected by CVE-2022-0735 across specific version ranges.

agent/references
agent/author
agent/type
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/12.0
version/gitlab/14.7
version/gitlab/14.8

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-0735?
CVE-2022-0735 has a high severity level due to the potential for unauthorized access to sensitive runner registration tokens.
How do I fix CVE-2022-0735?
To fix CVE-2022-0735, update GitLab to version 14.6.5 or later, version 14.7.4 or later, or version 14.8.2 or later.
Which versions are affected by CVE-2022-0735?
CVE-2022-0735 affects GitLab versions from 12.10 to 14.6.5, 14.7 to 14.7.4, and 14.8 to 14.8.2.
What type of vulnerability is CVE-2022-0735?
CVE-2022-0735 is an information disclosure vulnerability that allows unauthorized users to access sensitive tokens.
Is GitLab CE affected by CVE-2022-0735?
Yes, both GitLab CE and GitLab EE are affected by CVE-2022-0735 across specific version ranges.