dbcve.org
GitLabApplication

CVE-2022-2539

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 15.0.5 / 15.1.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 starting from 14.6 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1, allowed a project member to filter issues by contact and organization.

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

An authorization bypass in GitLab CE/EE versions 14.6 through 15.2.1 allowed project members to filter issues by contact and organization fields, exposing sensitive information that should have been restricted based on project membership access controls.

MitigationUpgrade GitLab to version 15.0.5, 15.1.4, 15.2.1 or later to patch the broken access control that permitted unauthorized filtering of issue metadata.

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:>= 14.6.0, < 15.0.5>= 15.1.0, < 15.1.4= 15.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin panel under /help for the exact version number
    Affected if The version falls within 14.6.0 to 15.0.4, 15.1.0 to 15.1.3, or exactly 15.2.0
  2. Confirm GitLab edition (CE or EE)
    Check the admin area dashboard or run `gitlab-rake gitlab:env:info` to see if the edition is Community Edition or Enterprise Edition
    Affected if The instance runs GitLab CE or EE (both editions are affected)
  3. Verify project member access to issue filtering
    As a project member with minimal permissions, attempt to access the issues list and apply filtering using contact or organization fields via API or web interface
    Affected if A project member can filter issues by contact or organization fields and view data from projects they do not normally have access to
  4. Check for unauthorized issue metadata exposure
    Compare what issue metadata a project member sees versus what a non-member sees when using contact/organization filters on shared projects
    Affected if Project members can view contact or organization information that should be restricted based on project membership access controls

The environment is affected if running GitLab CE/EE version 14.6.0 through 15.0.4, 15.1.0 through 15.1.3, or exactly 15.2.0, and project members can filter issues by contact or organization fields to access restricted information.

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.0.5 / 15.1.4 or later
Fixed in 15.0.515.1.4
Interim mitigation

Upgrade GitLab to version 15.0.5, 15.1.4, 15.2.1 or later to patch the broken access control that permitted unauthorized filtering of issue metadata.

Recommended fix High confidence

15.0.5, 15.1.4, or 15.2.1 (or later)

  1. 1. Back up your GitLab instance database and repositories
  2. 2. Review GitLab upgrade documentation for your current version
  3. 3. Stop GitLab services
  4. 4. Update GitLab using your package manager (e.g., apt-get update && apt-get install gitlab-ce for Debian/Ubuntu, or yum install for RHEL/CentOS)
  5. 5. Run sudo gitlab-ctl reconfigure
  6. 6. Verify GitLab is running and check the version at Help > Version
  7. 7. Confirm the vulnerability is resolved by verifying project members can no longer filter issues by contact/organization without proper permissions
Caveat Upgrading across major versions (e.g., 14.x to 15.x) may include breaking changes; review the GitLab 15.0 and 15.1 release notes for migration considerations

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2539 — 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-2539 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