dbcve.org
GitLabApplication

CVE-2022-3031

HIGH · 7.5 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.1.6 / 15.2.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue has been discovered in GitLab CE/EE affecting all versions before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2. It may be possible for an attacker to guess a user's password by brute force by sending crafted requests to a specific endpoint, even if the victim user has 2FA enabled on their account.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab CE/EE contains an authentication vulnerability where a specific endpoint can be targeted with brute force password guessing attacks. The flaw bypasses normal rate limiting protections and remains exploitable even against user accounts that have two-factor authentication (2FA) enabled, making it a significant authentication bypass.

MitigationUpgrade GitLab to version 15.3.2, 15.2.4, or 15.1.6 or later to remediate this vulnerability. If immediate upgrade is not possible, implement additional rate limiting at the network/load balancer level for the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:< 15.1.6>= 15.2, < 15.2.4>= 15.3, < 15.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin interface under Admin Area > Dashboard > Version. Alternatively, check the /opt/gitlab/version file if you have direct server access.
    Affected if Unable to retrieve version information (GitLab may not be installed or is not running)
  2. Identify the release branch
    Note the major.minor version number (e.g., 15.0, 15.1, 15.2, 15.3). If running a version before 15.0, you are on an older branch not listed in the affected ranges for this CVE but may have other issues.
    Affected if Version starts with 15.x (the affected release family)
  3. Compare against affected version ranges
    Determine if your specific version falls into any of these ranges: version < 15.1.6, OR version >= 15.2.0 and < 15.2.4, OR version >= 15.3.0 and < 15.3.2
    Affected if Your installed version matches any of the three affected ranges listed above

You are affected if your GitLab version falls within any of these ranges: < 15.1.6, >= 15.2.0 and < 15.2.4, or >= 15.3.0 and < 15.3.2.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.1.6 / 15.2.4 / 15.3.2 or later
Fixed in 15.1.615.2.415.3.2
Interim mitigation

Upgrade GitLab to version 15.3.2, 15.2.4, or 15.1.6 or later to remediate this vulnerability. If immediate upgrade is not possible, implement additional rate limiting at the network/load balancer level for the affected endpoint.

Recommended fix High confidence

Upgrade to GitLab 15.1.6, 15.2.4, or 15.3.2 (recommended: 15.3.2 or later for latest security patches)

  1. Schedule a maintenance window and back up your GitLab instance data
  2. Stop GitLab services before upgrade
  3. For Debian/Ubuntu: Run `sudo apt-get update && sudo apt-get install gitlab-ee` to upgrade to the latest fixed version
  4. For CentOS/RHEL: Run `sudo yum install gitlab-ee` to upgrade to the latest fixed version
  5. Alternatively, use Omnibus GitLab for direct upgrade: `sudo gitlab-ctl stop` then `curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash` followed by `sudo apt-get install gitlab-ee`
  6. After installation, run `sudo gitlab-ctl reconfigure` to apply configuration
  7. Start GitLab services with `sudo gitlab-ctl start`
  8. Verify the upgrade by checking GitLab version at Admin Area > Settings > General > GitLab version matches 15.1.6, 15.2.4, or 15.3.2 or later
Caveat Patch/minor upgrades within 15.x typically have minimal breaking changes; review GitLab release notes for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3031 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3031 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data