dbcve.org
GitLabApplication

CVE-2019-15583

HIGH · 7.5 CVSS v3.1 Published 2020-01-28
Fix available
A fix is available. Upgrade to 12.1.12 / 12.2.6 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 information disclosure exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE). When an issue was moved to a public project from a private one, the associated private labels and the private project namespace would be disclosed through the GitLab API.

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

When an issue is moved from a private project to a public project in affected GitLab versions, the API responds with the private labels and the private project namespace that should have remained confidential, resulting in unintended information disclosure.

MitigationUpgrade GitLab to version 12.3.2, 12.2.6, 12.1.12 or later to patch this information disclosure 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.1.0, < 12.1.12>= 12.2.0, < 12.2.6>= 12.3.0, < 12.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 installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Versions to find the exact version number
    Affected if The installed version falls within 12.1.0 to 12.1.11, 12.2.0 to 12.2.5, or 12.3.0 to 12.3.1
  2. Identify private-to-public project issue movements
    Review your GitLab instance for any issues that were moved from private projects to public projects using the API or UI
    Affected if Any issues have been moved from a private project to a public project
  3. Inspect API response for moved issues
    Use the GitLab API to query a moved issue: `curl --header "PRIVATE-TOKEN: <your-token>" "https://gitlab.example.com/api/v4/projects/<public-project-id>/issues/<issue-iid>"` and examine the response for any private labels or private project namespace references that should not be visible
    Affected if The API response contains private labels or private project namespace paths that belong to a private project

You are affected if your GitLab version is within the affected ranges AND you have moved issues from private to public projects, with private labels or namespace exposed in API responses.

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.

From vendor data
Upgrade available Upgrade to 12.1.12 / 12.2.6 / 12.3.2 or later
Fixed in 12.1.1212.2.612.3.2
Interim mitigation

Upgrade GitLab to version 12.3.2, 12.2.6, 12.1.12 or later to patch this information disclosure vulnerability.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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