Security readout for executives and security teams
Plain-English summary
This issue lets an attacker trick a GitLab administrator into pausing or resuming CI runners through a cross-site request forgery flaw. Business impact is limited to CI availability disruption, not code or data theft, based on the provided sources.
Executive priority
Handle through normal patch management unless CI availability is mission-critical. Escalate if affected GitLab instances support production deployment pipelines or regulated release processes.
Technical view
CVE-2020-13350 affects GitLab CE/EE versions >=13.5.0 <13.5.2, >=13.4.0 <13.4.5, and <13.3.9. The flaw is CSRF on the runner administration page, requiring administrator interaction. CVSS 3.1 is 3.1 with availability impact only.
Likely exposure
Exposure is most likely in self-managed GitLab CE/EE instances running the listed affected versions, especially where administrators manage CI runners through the web interface.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires targeting a GitLab instance administrator and inducing interaction, with impact limited to runner pause or resume state.
Researcher notes
No CWE is listed in the bundle. Public evidence describes CSRF behavior and affected ranges, but does not include detailed patch mechanics. Avoid assuming broader runner control beyond pause and resume.
Mitigation direction
- Upgrade GitLab CE/EE to a version outside the affected ranges.
- Check GitLab vendor guidance for the exact supported fixed release path.
- Prioritize CI runner availability checks after remediation.
- Reduce unnecessary administrator exposure to untrusted links or sessions.
Validation and detection
- Inventory GitLab CE/EE versions across all instances.
- Compare versions against the affected ranges in the CVE record.
- Review CI runner status for unexpected pause or resume changes.
- Confirm administrators can no longer reproduce unauthorized runner state changes.
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-13350 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
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L
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:H/PR:N/UI:R/S:U/C:N/I:N/A:L1.61.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.com/gitlab-org/gitlab/-/issues/24416CVE reference · x_refsource_MISC
- https://hackerone.com/reports/415238CVE reference · x_refsource_MISC
- https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13350.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.