GitLabApplication
CVE-2020-13358
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 · uneditedA vulnerability in the internal Kubernetes agent api in GitLab CE/EE version 13.3 and above allows unauthorized access to private projects. Affected versions are: >=13.4, <13.4.5,>=13.3, <13.3.9,>=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 confidenceGitLab's internal Kubernetes agent API has an access control flaw that allows unauthorized access to private projects. The vulnerability exists in the authentication/authorization logic of the Kubernetes agent feature, enabling attackers to potentially read private project data without proper credentials.
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
>= 13.3.0, < 13.3.9>= 13.3.0, <= 13.3.9>= 13.4.0, < 13.4.5>= 13.5.0, < 13.5.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionLog into GitLab as an administrator, navigate to Admin Area > Overview > Dashboard, and locate the version number displayed on the page. Alternatively, check the version file on the server (e.g., /opt/gitlab/version or gitlab-ctl version for Omnibus installations).Affected if The installed version falls within 13.3.0 to 13.3.9, 13.4.0 to 13.4.4, or 13.5.0 to 13.5.1.
-
Verify Kubernetes agent feature statusAs an administrator, go to Admin Area > Kubernetes > Clusters or check the .gitlab-ci.yml configurations in projects to see if any Kubernetes agent configurations exist. Also review project and group settings for enabled agents.Affected if The Kubernetes agent feature is enabled and configured for any project or group in the GitLab instance.
-
Review Kubernetes agent API access controlsExamine the GitLab logs (typically in /var/log/gitlab/gitlab-rails/production.log) for API calls to the Kubernetes agent endpoints that may indicate unauthorized access attempts to private projects.Affected if Unusual or unauthorized API access patterns to private projects via the Kubernetes agent are observed in logs.
You are affected if your GitLab version is between 13.3.0 and 13.3.9, 13.4.0 and 13.4.4, or 13.5.0 and 13.5.1, and the Kubernetes agent feature is actively enabled or configured.
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.3.913.4.513.5.2
Upgrade GitLab to version 13.4.5, 13.3.9, 13.5.2 or later to patch the vulnerability. Alternatively, disable the Kubernetes agent feature if not needed until upgrade is possible.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13358 — 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-13358 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