CVE-2020-13322 Vulnerability Analysis & Exploit Details

CVE-2020-13322
Vulnerability Scoring

7.2
/10
Very High Risk

Highly exploitable, CVE-2020-13322 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2020-13322 Details

Status: Analyzed

Last updated: 🕠 02 Oct 2020, 17:31 UTC
Originally published on: 🕕 30 Sep 2020, 18:15 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2020-13322 Vulnerability Summary

CVE-2020-13322: A vulnerability was discovered in GitLab versions after 12.9. Due to improper verification of permissions, an unauthorized user can create and delete deploy tokens.

Assessing the Risk of CVE-2020-13322

Access Complexity Graph

The exploitability of CVE-2020-13322 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2020-13322

The exploitability of CVE-2020-13322 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2020-13322, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2020-13322, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2020-13322 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2020-13322 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2020-13322 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.119% (probability of exploit)

EPSS Percentile: 47.7% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 52.3% of others.

CVE-2020-13322 References

External References

CWE Common Weakness Enumeration

CWE-863

Vulnerable Configurations

  • cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.0:*:*:*:-:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.8:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.8:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.9:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.9:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.9:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.9:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.10:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.10:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.9.10:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.9.10:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.0:*:*:*:-:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.2:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.2:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.8:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.8:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.9:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.9:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.9:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.9:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.10:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.10:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.10:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.10:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.11:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.11:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.11:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.11:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.12:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.12:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:12.10.12:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:12.10.12:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.0:*:*:*:-:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.3:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.3:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.4:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.4:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.5:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.5:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.6:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.6:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:-:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.0.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.0:*:*:*:-:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:community:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:community:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:-:*:*:*
    cpe:2.3:a:gitlab:gitlab:13.1.1:*:*:*:-:*:*:*

Protect Your Infrastructure against CVE-2020-13322: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...