GitLabApplication
CVE-2019-19312
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 · uneditedGitLab EE 8.14 through 12.5, 12.4.3, and 12.3.6 has Incorrect Access Control. After a project changed to private, previously forked repositories were still able to get information about the private project through the 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 · moderate confidenceGitLab EE versions 8.14 through 12.5, 12.4.3, and 12.3.6 had an incorrect access control vulnerability where forked repositories retained access to private project information via the API after the parent project was changed to private.
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
>= 8.14.0, < 12.3.8>= 12.4.0, < 12.4.5>= 12.5.0, < 12.5.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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or access Admin Area > Monitoring > Version Check in the web UI to retrieve the exact GitLab version numberAffected if Version is >= 8.14.0 and < 12.3.8, OR >= 12.4.0 and < 12.4.5, OR >= 12.5.0 and < 12.5.2
-
Verify fork feature is enabledCheck if any projects have the fork button enabled by navigating to Project > Settings > General > Visibility settings and confirming the 'Forks' toggle exists or by querying the database: `SELECT * FROM projects WHERE fork_network_member IS NOT NULL LIMIT 10;`Affected if Forking is enabled and forked projects exist in the instance
-
Identify forked projects with changed parent visibilityQuery the database to find projects that are forks: `SELECT p.id, p.path, p.visibility_level, fnm.forked_from_project_id FROM projects p JOIN fork_network_members fnm ON p.id = fnm.project_id;` then compare parent project visibility levels to identify any parents changed from public/internal to privateAffected if A fork exists where the parent project visibility was reduced to private after the fork was created (fork retains access it should not have)
-
Verify fork access via APIAs a user with access to a fork, attempt to query API endpoint `GET /api/v4/projects/:fork_id` and `GET /api/v4/projects/:fork_id/repository/tree` to confirm the fork can still access parent project data that should be privateAffected if The forked project can retrieve private project information from the original parent via API after parent was made private
User is affected if running a vulnerable GitLab version (8.14.0 to 12.5.2 range) and has forks where the parent project was changed to private, allowing the fork to retain unauthorized access to private data via API.
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.3.812.4.512.5.2
Upgrade GitLab to a patched version that resolves this access control bypass in fork-to-private project scenarios.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19312 — 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-19312 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