dbcve.org
GitLabApplication

CVE-2020-13346

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-07
Fix available
A fix is available. Upgrade to 13.2.10 / 13.3.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Membership changes are not reflected in ToDo subscriptions in GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2, allowing guest users to access confidential issues through 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 · high confidence

In GitLab versions prior to 13.2.10, 13.3.7, and 13.4.2, the ToDo subscription system does not properly synchronize with membership changes. When a user's project access is revoked or downgraded (e.g., from Developer to Guest), existing ToDo entries remain accessible via the API, allowing the now-revoked user to continue receiving notifications and accessing confidential issues they should no longer see.

MitigationUpgrade GitLab to version 13.2.10, 13.3.7, or 13.4.2 or later. Additionally, audit existing ToDo entries to ensure stale subscriptions for removed or downgraded users are revoked.

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:>= 11.2.0, < 13.2.10>= 13.3.0, < 13.3.7>= 13.4.0, < 13.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify GitLab version
    Log into the GitLab Admin area and navigate to the 'Version' section, or run 'gitlab-rake gitlab:env:info' from the server console. Look for the version number in the output.
    Affected if The installed version falls within these ranges: 11.2.0 to 13.2.9, 13.3.0 to 13.3.6, or 13.4.0 to 13.4.1. If the version is in any of these ranges, the instance is affected.
  2. Verify ToDo feature usage
    Query the todos table in the GitLab database to check for existing ToDo entries. Run: sudo gitlab-rails dbconsole -e production, then SELECT COUNT(*) FROM todos;
    Affected if If the ToDo table contains entries and the GitLab version is in the affected range listed above, the vulnerability may be present.
  3. Identify users with revoked or downgraded project access
    Review project membership audit logs in the Admin area under 'Audit Events' or query the project_members table for records where access_level has decreased or the member status is 'blocked' or 'deleted'. Use: SELECT user_id, project_id, access_level FROM project_members WHERE state != 'active';
    Affected if If users exist who have had their project access revoked or downgraded, and those users still have ToDo entries in the database, they may still be able to access those items via API.
  4. Check for orphaned ToDo entries
    Run a SQL query to find ToDo entries belonging to users who no longer have active project membership. Example: SELECT t.id, t.target_url, t.author_id FROM todos t LEFT JOIN project_members pm ON t.project_id = pm.project_id AND t.author_id = pm.user_id WHERE pm.id IS NULL AND t.target_type LIKE '%Issue%';
    Affected if If any ToDo entries are returned for users without active project membership, those users can still access those items through the API despite having insufficient permissions.

The environment is affected if GitLab version is between 11.2.0 and 13.2.9, 13.3.0 and 13.3.6, or 13.4.0 and 13.4.1 AND there exist ToDo entries belonging to users whose project access has been revoked or downgraded.

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.2.10 / 13.3.7 / 13.4.2 or later
Fixed in 13.2.1013.3.713.4.2
Interim mitigation

Upgrade GitLab to version 13.2.10, 13.3.7, or 13.4.2 or later. Additionally, audit existing ToDo entries to ensure stale subscriptions for removed or downgraded users are revoked.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13346 — 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-13346 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