GitLabApplication
CVE-2020-13284
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 was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. API Authorization Using Outdated CI Job Token
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 confidenceGitLab versions before 13.1.10, 13.2.8, and 13.3.4 contain a vulnerability where CI job tokens used for API authorization are not properly invalidated after they become outdated, allowing potentially unauthorized API access using stale tokens.
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.1.0, < 13.1.10>= 13.2.0, < 13.2.8>= 13.3.0, < 13.3.4CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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.
-
Check installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin panel under 'Help' > 'Version' to find the exact version numberAffected if Version is 13.1.0 to 13.1.9, 13.2.0 to 13.2.7, or 13.3.0 to 13.3.3 (not 13.1.10+, 13.2.8+, or 13.3.4+)
-
Determine if CI job tokens are in useReview your GitLab CI/CD pipelines and look for any jobs that make API calls using the CI_JOB_TOKEN variable, or check for external integrations that authenticate using CI job tokensAffected if CI pipelines or integrations rely on CI_JOB_TOKEN for API authorization
-
Inspect token expiration and rotation settingsCheck GitLab admin settings under 'CI/CD' > 'Runners' and review whether job tokens have automatic expiration enabled, or search API audit logs for token usage patternsAffected if Job tokens are allowed to persist without proper invalidation after pipeline completion
-
Review audit logs for stale token usageAccess GitLab's audit log (Admin Area > Monitoring > Audit Events) and search for API calls using job tokens from completed pipelines, particularly those that ran before upgradingAffected if API activity is logged from job tokens after their associated pipeline jobs have finished
You are affected if your GitLab version is within the vulnerable range (13.1.0-13.1.9, 13.2.0-13.2.7, or 13.3.0-13.3.3) and CI job tokens have been used for API authentication, as stale tokens may still be valid.
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.1.1013.2.813.3.4
Upgrade GitLab to version 13.1.10, 13.2.8, 13.3.4 or later. Alternatively, review and rotate any CI job tokens that may have been exposed or used prior to patching.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13284 — 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-13284 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