CVE-2020-15123 Vulnerability Analysis & Exploit Details

CVE-2020-15123
Vulnerability Scoring

9.3
/10
Critical Risk

As a catastrophic security flaw, CVE-2020-15123 has severe implications, demanding immediate intervention.

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: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2020-15123 Details

Status: Analyzed

Last updated: 🕖 27 Jul 2020, 19:00 UTC
Originally published on: 🕕 20 Jul 2020, 18:15 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2020-15123 Vulnerability Summary

CVE-2020-15123: In codecov (npm package) before version 3.7.1 the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was issued but the fix was incomplete. It only blocked &, and command injection is still possible using backticks instead to bypass the sanitizer. The attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.

Assessing the Risk of CVE-2020-15123

Access Complexity Graph

The exploitability of CVE-2020-15123 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-15123

With low attack complexity and no required privileges, CVE-2020-15123 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-15123, 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-15123, 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-15123 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2020-15123 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2020-15123 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 3.264% (probability of exploit)

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

CVE-2020-15123 References

External References

CWE Common Weakness Enumeration

CWE-78

CAPEC Common Attack Pattern Enumeration and Classification

  • Command Line Execution through SQL Injection CAPEC-108 An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Argument Injection CAPEC-6 An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
  • OS Command Injection CAPEC-88 In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.

Vulnerable Configurations

  • cpe:2.3:a:codecov:codecov:0.0.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.6:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.6:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.8:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.8:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.9:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.9:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.11:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.11:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.0.12:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.0.12:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.6:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.6:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.7:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.7:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.8:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.8:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.9:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.9:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.10:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.10:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.11:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.11:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.12:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.12:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.13:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.13:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.14:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.14:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.15:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.15:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.16:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.16:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.17:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.17:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.18:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.18:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.19:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.19:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.20:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.20:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.1.21:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.1.21:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.6:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.6:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.7:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.7:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.8:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.8:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.9:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.9:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.10:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.10:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.11:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.11:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.12:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.12:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.13:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.13:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.14:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.14:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.2.15:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.2.15:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.3.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.3.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.4.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.4.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.4.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.4.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.4.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.4.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.4.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.4.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.5.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.5.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.5.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.5.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.5.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.5.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:0.6.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:codecov:codecov:0.6.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:codecov:codecov:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:2.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:2.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.6.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.6.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:codecov:codecov:3.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:codecov:codecov:3.7.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2020-15123: 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-3805 – A vulnerability classified as critical was found in sarrionandia tournatrack up to 4c13a23f43da5317eea4614870a7a8510fc540ec. Affected by this vulne...
  • CVE-2025-3804 – A vulnerability classified as critical has been found in thautwarm vscode-diana 0.0.1. Affected is an unknown function of the file Gen.py of the co...
  • CVE-2025-3803 – A vulnerability was found in Tenda W12 and i24 3.0.0.4(2887)/3.0.0.5(3644). It has been rated as critical. This issue affects the function cgiSysSc...
  • CVE-2025-3802 – A vulnerability was found in Tenda W12 and i24 3.0.0.4(2887)/3.0.0.5(3644). It has been declared as critical. This vulnerability affects the functi...
  • CVE-2025-3801 – A vulnerability was found in songquanpeng one-api up to 0.6.10. It has been classified as problematic. This affects an unknown part of the componen...