CVE-2022-0735

Description

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.

10.0

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 53.60% Top 5%

Vendor Advisory gitlab.com

Affected: GitLab GitLab

References

Link	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/353529	broken link
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-0735.json	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-0735?: CVE-2022-0735 has been scored as a critical severity vulnerability.
How to fix CVE-2022-0735?: To fix CVE-2022-0735, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0735 being actively exploited in the wild?: It is possible that CVE-2022-0735 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~54% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0735?: CVE-2022-0735 affects GitLab GitLab.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.