GitLabApplication
CVE-2020-13334
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 · uneditedIn GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2, improper authorization checks allow a non-member of a project/group to change the confidentiality attribute of issue via mutation GraphQL query
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 confidenceImproper authorization checks in GitLab versions prior to 13.2.10, 13.3.7, and 13.4.2 allow non-members of a project or group to modify the confidentiality attribute of issues through a GraphQL mutation query, potentially exposing sensitive information.
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.6.0, < 13.2.10>= 13.3.0, < 13.3.7>= 13.4.0, < 13.4.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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area at /admin/application_settings or review /opt/gitlab/version-manifest.txtAffected if The displayed version falls within the vulnerable ranges: < 13.2.10, >= 13.3.0 and < 13.3.7, or >= 13.4.0 and < 13.4.2
-
Verify GitLab component version consistencyRun `sudo gitlab-rake gitlab:git:version` to confirm the underlying Git version matches the reported GitLab versionAffected if There is a mismatch that prevents accurate version determination, or the version confirms the vulnerability
-
Confirm GraphQL API is accessibleAttempt to access the GraphQL endpoint at /api/graphql (e.g., curl -k https://your-gitlab/api/graphql)Affected if The GraphQL endpoint responds and accepts mutation queries, making the authorization flaw exploitable
-
Review project and group membership settingsCheck the project or group settings at /project/-/settings or /group/-/settings to identify whether external users or non-members have any accessAffected if Projects or groups allow access to users who are not members, combined with a vulnerable GitLab version
A user is affected if their GitLab version is below 13.2.10, between 13.3.0-13.3.6, or between 13.4.0-13.4.1 AND the GraphQL API is exposed to non-members who can submit mutation queries.
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 data13.2.1013.3.713.4.2
Upgrade GitLab to version 13.2.10, 13.3.7, 13.4.2 or later to implement proper authorization validation on the issue confidentiality GraphQL mutation.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13334 — 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-2020-13334 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