GitLabApplication
CVE-2019-18452
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.3 through 12.4 when moving an issue to a public project from a private one. It has Insecure Permissions.
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.3 through 12.4 contain an insecure permissions vulnerability where moving an issue from a private project to a public project fails to properly enforce access controls, potentially exposing private issue content (titles, descriptions, comments, attachments) to unauthorized public users.
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.3.0, <= 12.4.0CVSS 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 check the GitLab admin panel under 'Admin Area > Application > GitLab version' to determine the exact version numberAffected if Version is 11.3.0 through 12.4.0 inclusive (versions before 11.3.0 or after 12.4.0 are not affected)
-
Identify issues moved between projectsQuery the GitLab database: `SELECT id, title, state, moved_to_from_project_id, moved_to_project_id FROM issues WHERE moved_to_project_id IS NOT NULL OR moved_to_from_project_id IS NOT NULL;` This requires database accessAffected if Any issue move records exist where an issue was moved from a private project (moved_to_from_project_id) to a public project (moved_to_project_id)
-
Review audit logs for issue move operationsCheck GitLab audit logs under 'Admin Area > Audit Events' or query the audit_events table for event_type 'issue_move' or similar issue transfer events during the vulnerable periodAffected if Audit logs show issues were moved from private to public projects between versions 11.3 and 12.4
-
Check for public projects that received issuesList all public projects using the GitLab API (`GET /projects?visibility=public`) or admin interface, then cross-reference with moved issue records to identify public projects that received issues from private projectsAffected if Any public project contains issues that originated from private projects during the vulnerable version period
The environment is affected if GitLab version is between 11.3.0 and 12.4.0 AND issues were moved from private projects to public projects during that time.
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 dataUpgrade GitLab to version 12.5 or later. Review audit logs and any issues that may have been moved from private to public projects during the vulnerable period to identify and remediate any exposed sensitive information.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18452 — 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-18452 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