GitLabApplication
CVE-2019-15732
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 12.2 through 12.2.1. The project import API could be used to bypass project visibility restrictions.
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 confidenceIn GitLab 12.2 through 12.2.1, the project import API contained a logic flaw that allowed users to bypass project visibility restrictions. This likely allowed lower-privileged users to create projects with higher visibility (e.g., internal or public) than their permissions would normally allow, by exploiting the import functionality instead of direct project creation.
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.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.
-
Check installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin dashboard under Help > Version to obtain the exact version numberAffected if Version is 12.2.0, 12.2.1, or 12.2.2 (pre-fix releases within >= 12.2.0 and < 12.2.3)
-
Verify project import/export feature is accessibleAs an administrator, navigate to Admin Area > Settings > Visibility and access controls > Import sources. Confirm that project import options are enabled for usersAffected if Import sources are enabled and non-admin users have access to the import functionality
-
Review audit logs for suspicious project creation via importNavigate to Admin Area > Audit Events and filter by event type 'project_import' or 'project_create'. Look for projects created with internal or public visibility by users who lack the permission to set such visibility directlyAffected if Audit logs show projects with internal or public visibility created through import by users who only have reporter, developer, or maintainer roles
-
Check for projects with visibility that exceeds user permissionsQuery the projects table or use the API `GET /projects?min_access_level=10` to list projects. Cross-reference with their creators' maximum allowed visibility level in the databaseAffected if Projects exist with internal or public visibility where the creator's role should only permit private or internal visibility
A user is affected if their GitLab instance runs version 12.2.0 through 12.2.2 and non-admin users have access to the project import feature.
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.2.3
Upgrade GitLab to version 12.2.2 or later, which contains the fix for proper enforcement of visibility restrictions during project import operations.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15732 — 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-15732 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