dbcve.org
GitLabApplication

CVE-2020-13352

MEDIUM · 5.3 CVSS v3.1 Published 2020-11-17
Fix available
A fix is available. Upgrade to 13.3.9 / 13.4.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Private group info is leaked leaked in GitLab CE/EE version 10.2 and above, when the project is moved from private to public group. Affected versions are: >=10.2, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.

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 confidence

In GitLab CE/EE versions 10.2 through 13.5.2, private group information is inadvertently leaked when a project is moved from a private group to a public group, exposing sensitive group metadata that should remain confidential.

MitigationUpgrade GitLab to version 13.3.9, 13.4.5, 13.5.2 or later to patch the vulnerability, and audit group/project visibility settings for potential exposure.

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
Affected:>= 10.2.0, < 13.3.9>= 13.4.0, < 13.4.5>= 13.5.0, < 13.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/application_settings or look at /opt/gitlab/version-manifest.txt
    Affected if Version is >= 10.2.0 and < 13.3.9, OR >= 13.4.0 and < 13.4.5, OR >= 13.5.0 and < 13.5.2
  2. Review audit logs for project move events
    In GitLab admin go to Admin Area > Monitoring > Audit Events, or use API: GET /audit_events with entity_type: Project and filter for 'transfer' or 'move' action types
    Affected if Any project transfer events exist where a project was moved from a private group namespace to a public group or public namespace
  3. Check for projects in public groups that originated from private groups
    Query the database: SELECT projects.path, namespaces.path AS group_path, projects.visibility FROM projects JOIN namespaces ON projects.namespace_id = namespaces.id WHERE namespaces.type = 'Group' AND namespaces.visibility = 'public' AND EXISTS (SELECT 1 FROM project_group_links WHERE project_id = projects.id); Or use GitLab API to list all public projects and manually review their namespace history
    Affected if Projects exist in public groups that were previously under private groups, or project_group_links show unexpected associations
  4. Verify group membership exposure
    Check if any private group names, member emails, or group-level labels/Boards data appear in public project artifacts, wikis, or issues. Review public project activity for leaked group references.
    Affected if Private group metadata (group names, member details, internal labels) appears in any public-facing project content
  5. Check project namespace history
    Use GitLab API: GET /projects/:id or database query on projects table for route history, or check /admin/projects/:id/transfer for any transfer records
    Affected if Project records show a previous private group_id in the route history or transfer logs

A user is affected if their GitLab version falls within the vulnerable ranges AND any project has been moved from a private group to a public group, as private group metadata may have been exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 13.3.9 / 13.4.5 / 13.5.2 or later
Fixed in 13.3.913.4.513.5.2
Interim mitigation

Upgrade GitLab to version 13.3.9, 13.4.5, 13.5.2 or later to patch the vulnerability, and audit group/project visibility settings for potential exposure.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13352 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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