Security readout for executives and security teams
Plain-English summary
GitLab had a permissions flaw that could let an authenticated user read scheduled pipeline variable names and values in projects they could see. If those variables held secrets, tokens, or deployment credentials, the business risk is credential exposure, not service disruption.
Executive priority
Treat as a moderate confidentiality issue. Prioritize remediation where GitLab stores production secrets, deployment tokens, cloud credentials, or customer-impacting automation variables.
Technical view
CVE-2020-13351 affects GitLab CE/EE 13.0+ within specified 13.3, 13.4, and 13.5 release ranges. The scheduled pipeline API lacked sufficient permission checks, allowing low-privileged authenticated access to confidential variable names and values for visible projects.
Likely exposure
Exposure is limited to GitLab CE/EE instances running affected versions and projects visible to the attacker with scheduled pipeline variables configured.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Public GitLab and HackerOne references exist, so defenders should assume vulnerability details were publicly discoverable after disclosure.
Researcher notes
No CWE is listed in the bundle. CVSS 3.1 is 6.5 with low attack complexity, low privileges, no user interaction, and high confidentiality impact. Evidence supports data exposure, not integrity or availability impact.
Mitigation direction
- Upgrade GitLab CE/EE outside the affected version ranges.
- Check GitLab guidance for the exact supported fixed release path.
- Review scheduled pipeline variables for secrets or privileged tokens.
- Rotate sensitive variable values that may have been exposed.
- Reduce project visibility where broad visibility is unnecessary.
Validation and detection
- Inventory all GitLab CE/EE instance versions.
- Confirm no instance runs 13.0 to affected 13.5 releases.
- Identify projects with scheduled pipelines and stored variables.
- Review access exposure for visible projects containing scheduled pipeline variables.
- Verify upgraded instances follow GitLab’s fixed maintenance versions or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-13351 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.com/gitlab-org/gitlab/-/issues/239369CVE reference · x_refsource_MISC
- https://hackerone.com/reports/962462CVE reference · x_refsource_MISC
- https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13351.jsonCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.