CVE-2022-2303

Description

An issue has been discovered in GitLab CE/EE affecting all versions before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. It may be possible for group members to bypass 2FA enforcement enabled at the group level by using Resource Owner Password Credentials grant to obtain an access token without using 2FA.

Category

4.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.02%
Vendor Advisory gitlab.com Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/355028 broken link vendor advisory
https://hackerone.com/reports/1498133 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2303.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-2303?
CVE-2022-2303 has been scored as a medium severity vulnerability.
How to fix CVE-2022-2303?
To fix CVE-2022-2303, 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-2303 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-2303 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-2303?
CVE-2022-2303 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.
© 2025 Under My Watch. All Rights Reserved.