GitLabApplication
CVE-2019-15727
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 issue was discovered in GitLab Community and Enterprise Edition 11.2 through 12.2.1. Insufficient permission checks were being applied when displaying CI results, potentially exposing some CI metrics data to unauthorized users.
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 versions 11.2 through 12.2.1 had insufficient permission checks in the CI results display functionality. This allowed unauthorized users to potentially view CI metrics data they should not have access to, representing an authorization bypass vulnerability in the Continuous Integration module.
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
>= 11.2.0, < 12.0.8>= 12.1.0, < 12.1.8>= 12.2.0, < 12.2.3CVSS 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.
-
Identify installed GitLab versionAccess the GitLab admin panel or use the GitLab API (e.g., /api/v4/version) to retrieve the running version numberAffected if The version falls within 11.2.0 to 12.0.7, 12.1.0 to 12.1.7, or 12.2.0 to 12.2.2
-
Confirm CI module is activeVerify that the GitLab instance has Continuous Integration pipelines configured by checking if any projects contain .gitlab-ci.yml files or have CI pipeline historyAffected if CI pipelines exist and the instance uses the vulnerable version
-
Check project visibility settingsReview project settings in the GitLab UI under Settings > Visibility to see which projects have CI job results that could be accessedAffected if Projects with CI pipelines have more permissive visibility settings than 'Private' (such as Internal or Public)
The environment is affected if GitLab version is 12.0.7 or earlier, 12.1.7 or earlier, or 12.2.2 or earlier AND CI pipelines are configured on the instance.
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.0.812.1.812.2.3
Upgrade GitLab to version 12.2.2 or later. Alternatively, if immediate upgrade is not feasible, review access controls on CI job results and restrict project visibility settings as a temporary compensating control until the upgrade can be performed.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15727 — 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-15727 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