dbcve.org
GitLabApplication

CVE-2022-2761

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 15.3.5 / 15.4.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 information disclosure issue in GitLab CE/EE affecting all versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to use GitLab Flavored Markdown (GFM) references in a Jira issue to disclose the names of resources they don't have access to.

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 information disclosure vulnerability in GitLab's Jira integration where an attacker can embed GitLab Flavored Markdown (GFM) references in a Jira issue. When the Jira issue is rendered, GitLab returns metadata (including resource names) for referenced items the attacker shouldn't have access to, allowing enumeration of protected resource names.

MitigationUpgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later. This is a server-side patch that corrects how GFM references are processed in the Jira integration context.

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:>= 13.9.0, < 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.5.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 GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, navigate to Admin Area > Dashboard in the web UI and locate the version number at the bottom.
    Affected if Version falls within 13.9.0 to 15.3.4, 15.4.0 to 15.4.3, or 15.5.0 to 15.5.1
  2. Verify Jira integration is enabled
    Navigate to Admin Area > Applications > Applications and look for any Jira-linked applications. Alternatively, check Project Settings > Integrations > Jira for any enabled integrations.
    Affected if Jira integration is active and linked to a GitLab project
  3. Confirm Jira projects are linked
    Go to Project Settings > Integrations > Jira and review the 'Jira projects' field. Check if any Jira project keys are listed under 'Selected projects'.
    Affected if At least one Jira project is linked to the GitLab instance
  4. Check external exposure
    Review network access controls. Determine whether the GitLab instance is accessible from untrusted networks where an external attacker could create or modify Jira issues.
    Affected if GitLab or Jira is accessible from networks where untrusted users can create or modify Jira issues containing GFM references

If the GitLab version is in an affected range AND Jira integration is enabled with linked projects, the environment is vulnerable to information disclosure through GFM reference enumeration in Jira issues.

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.3.5 / 15.4.4 / 15.5.2 or later
Fixed in 15.3.515.4.415.5.2
Interim mitigation

Upgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later. This is a server-side patch that corrects how GFM references are processed in the Jira integration context.

Recommended fix High confidence

Upgrade to GitLab 15.3.5, 15.4.4, or 15.5.2 (or later stable release)

  1. Back up the GitLab database and repositories
  2. Stop the GitLab service
  3. Update GitLab to version 15.3.5 (if on 15.3.x), 15.4.4 (if on 15.4.x), or 15.5.2 (if on 15.5.x) using the official upgrade method (package manager or source)
  4. Run 'gitlab-ctl reconfigure' after the package update
  5. Start the GitLab service
  6. Verify the upgrade was successful and GitLab is functioning properly
Caveat Minor: GitLab patch upgrades typically have no breaking changes; always review release notes for any specific considerations

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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