dbcve.org
GitLabApplication

CVE-2022-2907

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-17
Fix available
A fix is available. Upgrade to 15.1.6 / 15.2.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 12.9 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 was possible to read repository content by an unauthorised user if a project member used a crafted link.

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 IDOR vulnerability in GitLab CE/EE allowed unauthorized users to read repository content via a crafted link shared by a project member. The flaw permitted bypass of access controls by manipulating URLs or parameters to access repository data outside authorized scope.

MitigationUpgrade GitLab to version 15.1.6, 15.2.4, or 15.3.2 or later to patch the unauthorized repository access vulnerability.

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:>= 12.9, < 15.1.6>= 12.9, <= 15.1.6>= 15.2.0, < 15.2.4>= 15.3.0, < 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the Admin Area > Settings > General page for the version number
    Affected if The displayed version falls within 12.9 to 15.1.5, 15.2.0 to 15.2.3, or 15.3.0 to 15.3.1
  2. Confirm GitLab component version
    Check /opt/gitlab/embedded/gitlab-rails/VERSION file or run `gitlab --version` to verify the exact version string
    Affected if Version matches any of the affected ranges listed in the CVE (all versions from 12.9 up to the patched versions)
  3. Identify if external user sharing is enabled
    Navigate to Admin Area > Settings > General > Visibility and access control > Project feature settings, or inspect gitlab.yml configuration for share_project_enabled parameter
    Affected if Project/repository sharing is enabled (this is the attack vector for the IDOR)

A GitLab installation is affected if it runs any version from 12.9 through 15.1.5, 15.2.0 through 15.2.3, or 15.3.0 through 15.3.1 and has sharing features enabled.

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.1.6, 15.2.4, or 15.3.2 or later to patch the unauthorized repository access vulnerability.

Recommended fix High confidence

15.1.6, 15.2.4, or 15.3.2 depending on your current major.minor version

  1. 1. Backup your GitLab instance and database before upgrading.
  2. 2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area.
  3. 3. For GitLab 15.1.x: Upgrade to version 15.1.6 or later.
  4. 4. For GitLab 15.2.x: Upgrade to version 15.2.4 or later.
  5. 5. For GitLab 15.3.x: Upgrade to version 15.3.2 or later.
  6. 6. For older versions (12.9 to 15.0.x): Upgrade to one of the fixed versions listed above, passing through any intermediate required upgrades per GitLab's upgrade path documentation.
  7. 7. After upgrade, verify the fix by testing that unauthorized users cannot access repository content via crafted links.
  8. 8. Review user project memberships and revoke any unnecessary access.
Caveat Standard GitLab upgrade considerations apply - review release notes for breaking changes between your current version and target version

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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