GitLabApplication
CVE-2019-15579
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 · uneditedAn information disclosure exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) where the assignee(s) of a confidential issue in a private project would be disclosed to a guest via milestones.
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 confidenceGitLab CE/EE before versions 12.1.12, 12.2.6, and 12.3.2 contains an information disclosure vulnerability where guest users can view the assignee(s) of confidential issues in private projects through the milestones feature. This is a broken access control issue where authorization checks are not properly enforced when displaying milestone-related information to users with guest-level permissions.
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
>= 12.1.0, < 12.1.12>= 12.2.0, < 12.2.6>= 12.3.0, < 12.3.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionRun `gitlab-rake gitlab:env:info` or inspect `/opt/gitlab/version` to obtain the exact GitLab version numberAffected if The 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
-
Identify guest users in private projectsQuery the GitLab database or use the UI to list users with Guest role assigned to private projectsAffected if Guest users exist in any private project that contains confidential issues
-
Locate confidential issues with assigneesSearch for confidential issues (issues with 'confidential' flag enabled) that have one or more users assigned, typically via the GitLab API or database query on the issues table where confidential = true and assignee_ids is not nullAffected if Confidential issues with assignees exist in private projects accessible to guest users
-
Verify milestone access for guestsAs a guest user, navigate to the milestones page of an affected private project and attempt to view issue assignee information through the milestone interfaceAffected if Guest users can see assignee usernames or avatars on confidential issues when viewing milestone-related issue lists
A user is affected if running a GitLab version in the vulnerable range AND guest users can access confidential issue assignees through the milestones feature in private projects.
Generated from the published advisory. Verify against your own configuration.
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 data12.1.1212.2.612.3.2
Upgrade GitLab to version 12.3.2 or later (for the 12.3.x branch), 12.2.6 or later (for the 12.2.x branch), or 12.1.12 or later (for the 12.1.x branch). For GitLab.com users, no action is required as the fix is deployed centrally.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15579 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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