GitLabApplication
CVE-2020-13351
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 · uneditedInsufficient permission checks in scheduled pipeline API in GitLab CE/EE 13.0+ allows an attacker to read variable names and values for scheduled pipelines on projects visible to the attacker. Affected versions are >=13.0, <13.3.9,>=13.4.0, <13.4.5,>=13.5.0, <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 confidenceInsufficient permission checks in GitLab's scheduled pipeline API allow authenticated users who can view a project to read sensitive variable names and values from scheduled pipeline configurations through the API, exposing potentially secret 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.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check your GitLab versionNavigate to the GitLab admin panel (Admin Area > Overview > Dashboard) or use the API endpoint /api/v4/version to retrieve the installed GitLab version number.Affected if The installed version falls within any of these ranges: 13.0.0 to 13.3.8, 13.4.0 to 13.4.4, or 13.5.0 to 13.5.1.
-
Identify projects with scheduled pipelinesUse the GitLab API (GET /projects/:id/pipelines) or navigate to each project is CI/CD > Pipelines > Schedules to see if any scheduled pipelines exist.Affected if Any scheduled pipeline exists in your GitLab instance.
-
Inspect variables in scheduled pipelinesFor each scheduled pipeline, navigate to its configuration and review any CI/CD variables defined. Access via the web UI at Project > CI/CD > Pipelines > Schedules > [Select Schedule] > Edit or via the API endpoint GET /projects/:id/pipeline_schedules/:id.Affected if Scheduled pipelines contain CI/CD variables, particularly those marked as masked or protected.
-
Review project member access levelsNavigate to Project > Settings > Members or use the API GET /projects/:id/members to list all users with access to projects containing scheduled pipelines.Affected if Projects with scheduled pipelines have members beyond the direct team (such as guests, reporters, or external users) who can view the project.
You are affected if your GitLab version is within the vulnerable ranges AND you have scheduled pipelines containing CI/CD variables in projects accessible to users who should not see sensitive variable values.
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.3.9, 13.4.5, or 13.5.2 or later. Until upgraded, avoid storing sensitive variables in scheduled pipelines for projects with untrusted members.
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-13351 — 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-13351 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