dbcve.org
GitLabApplication

CVE-2022-1352

MEDIUM · 5.3 CVSS v3.1 Published 2022-05-11
Fix available
A fix is available. Upgrade to 14.8.6 / 14.9.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
Due to an insecure direct object reference vulnerability in Gitlab EE/CE affecting all versions from 11.0 prior to 14.8.6, 14.9 prior to 14.9.4, and 14.10 prior to 14.10.1, an endpoint may reveal the issue title to a user who crafted an API call with the ID of the issue from a public project that restricts access to issue only to project members.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in GitLab where an endpoint fails to properly enforce authorization checks. A user can craft an API request using an issue ID from a public project where issue access is restricted to project members only, and the API will return the issue title to the unauthorized user, resulting in information disclosure.

MitigationUpgrade GitLab to versions 14.8.6, 14.9.4, 14.10.1 or later to receive the patched code that properly enforces authorization checks on 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:>= 11.0.0, < 14.8.6>= 14.9.0, < 14.9.4= 14.10.0

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. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or `cat /opt/gitlab/version` or view the version in the GitLab admin area under Help > Version
    Affected if The installed version falls within >= 11.0.0 and < 14.8.6, OR >= 14.9.0 and < 14.9.4, OR equals 14.10.0
  2. Identify public projects with restricted issue access
    In GitLab UI, go to Project > Settings > General > Visibility and verify if any public projects have Issues set to 'Only project members' or similar restricted access
    Affected if There exist public projects where issue visibility is restricted to project members only
  3. Test API endpoint authorization for issue titles
    Using a non-member or unauthenticated account, send a GET request to the GitLab API endpoint for issues (e.g., `GET /api/v4/projects/:id/issues/:issue_id`) for a public project with restricted issue access
    Affected if The API response returns the issue title or any issue details to the unauthorized user when it should deny access

A user is affected if their GitLab version is vulnerable AND they have public projects where issue access is restricted to members, allowing unauthorized API requests to disclose issue titles.

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 14.8.6 / 14.9.4 or later
Fixed in 14.8.614.9.4
Interim mitigation

Upgrade GitLab to versions 14.8.6, 14.9.4, 14.10.1 or later to receive the patched code that properly enforces authorization checks on the affected endpoint.

Recommended fix High confidence

14.10.1, or 14.9.4, or 14.8.6 (choose the appropriate release line for your environment)

  1. Back up your GitLab instance database and repositories
  2. Plan your upgrade path according to your current version (see upgrade_path)
  3. For installations using the official GitLab packages, run: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise)
  4. Alternatively, if using Docker: pull the new image and recreate containers
  5. Alternatively, if using source: stop GitLab, download the new version from gitlab.com, extract, and run the upgrade scripts
  6. Verify the upgrade completed successfully by checking the GitLab version in the Admin Area or via the API
  7. Test that the IDOR vulnerability is patched by confirming external users can no longer access restricted issue titles via API
Caveat Minor version upgrades within the same major release (e.g., 14.x) typically do not introduce breaking changes; always review GitLab release notes before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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