CVE-2022-2303Public exploitNetwork attack vector

Group 2FA bypass via OAuth password grant

Published Aug 5, 2022 · Updated Aug 3, 2024

Improper authentication in GitLab CE/EE allows remote authenticated users to bypass group-level 2FA enforcement through OAuth. The OAuth password grant issues an access token from a group member's username and password without applying the group's 2FA requirement, and that token retains API access to protected group resources. The attacker must already be a group member with valid credentials while an owner has enabled group-level 2FA enforcement; granted scopes permit reading confidential group data and altering resources.

CVSS severity4.3
Medium
EPSS probability0.75%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in GitLab CE/EE allows remote authenticated users to bypass group-level 2FA enforcement through OAuth. The OAuth password grant issues an access token from a group member's username and password without applying the group's 2FA requirement, and that token retains API access to protected group resources. The attacker must already be a group member with valid credentials while an owner has enabled group-level 2FA enforcement; granted scopes permit reading confidential group data and altering resources.

The record

CVE
CVE-2022-2303
Published
Aug 5, 2022
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-287, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 5, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=0.0, <15.0.5
  2. Affected versionversion=>=15.1, <15.1.4
  3. Affected versionversion=>=15.2, <15.2.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=0.0, <15.0.5; version=>=15.1, <15.1.4; version=>=15.2, <15.2.1

Published CVSS scores

4.3GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-287Improper Authentication
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo