LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13348: An issue has been discovered in GitLab EE affecting all versions starting from 10.2.

An issue has been discovered in GitLab EE affecting all versions starting from 10.2. Required CODEOWNERS approval could be bypassed by targeting a branch without the CODEOWNERS file. Affected versions are >=10.2, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.

MediumCVSS 5.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-13348 is a GitLab EE authorization flaw where required CODEOWNERS approval could be bypassed by targeting a branch that lacked a CODEOWNERS file. Business impact is unauthorized code changes bypassing governance controls, not data theft or service outage based on the provided CVSS vector.

Executive priority

Treat this as a governance and code-integrity risk. It is not rated critical, but organizations using CODEOWNERS for production change control, regulated workflows, or separation of duties should remediate promptly.

Technical view

Affected GitLab EE versions are >=10.2 to <13.3.9, >=13.4 to <13.4.5, and >=13.5 to <13.5.2. The issue is network-reachable, low-complexity, requires low privileges and user interaction, and has high integrity impact with no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to GitLab EE deployments in the affected version ranges, especially projects that rely on CODEOWNERS approval as a release, compliance, or protected-branch control.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation would depend on an authenticated context and a workflow where CODEOWNERS approval is required but the targeted branch lacks the CODEOWNERS file.

Researcher notes

The available evidence describes the bypass condition and affected ranges but does not include CWE mapping, exploit status, or detailed remediation text. Analysis is therefore constrained to version exposure, integrity impact, and CODEOWNERS approval workflow validation.

Mitigation direction

  • Upgrade GitLab EE outside the affected version ranges.
  • Prioritize versions 13.3.9, 13.4.5, 13.5.2, or later where applicable.
  • Check current GitLab vendor guidance before scheduling remediation.
  • Review projects relying on CODEOWNERS approval for governance.
  • Ensure protected approval workflows are consistently configured across relevant branches.

Validation and detection

  • Inventory GitLab EE instances and record exact versions.
  • Confirm no instance matches the affected version ranges.
  • Identify projects where CODEOWNERS approval is required.
  • Review whether relevant target branches contain expected CODEOWNERS controls.
  • Audit recent merges where CODEOWNERS approval should have applied.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2020-13348 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.7Medium
CVSS 3.1 vector shape for CVE-2020-13348Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab EE>=10.2, <13.3.9, >=13.4, <13.4.5, >=13.5, <13.5.2Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.