CVE-2019-10800 Vulnerability Analysis & Exploit Details

CVE-2019-10800
Vulnerability Scoring

6.5

/10

High Risk

If left unpatched, CVE-2019-10800 could lead to major system disruptions or data loss.

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: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2019-10800 Details

Status: Analyzed

Last updated: 🕒 08 Nov 2022, 03:09 UTC
Originally published on: 🕛 13 Jul 2022, 12:15 UTC

Time between publication and last update: 117 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-10800 Vulnerability Summary

CVE-2019-10800: This affects the package codecov before 2.0.16. The vulnerability occurs due to not sanitizing gcov arguments before being being provided to the popen method.

Assessing the Risk of CVE-2019-10800

Access Complexity Graph

The exploitability of CVE-2019-10800 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-2019-10800

CVE-2019-10800 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-2019-10800, 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-2019-10800, 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-2019-10800 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: None
CVE-2019-10800 poses no threat to data integrity.
Availability: None
CVE-2019-10800 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: 0.107% (probability of exploit)

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

CVE-2019-10800 References

External References

CWE Common Weakness Enumeration

CWE-88

CAPEC Common Attack Pattern Enumeration and Classification

Parameter Injection CAPEC-137 An adversary manipulates the content of request parameters for the purpose of undermining the security of the target. Some parameter encodings use text characters as separators. For example, parameters in a HTTP GET message are encoded as name-value pairs separated by an ampersand (&). If an attacker can supply text strings that are used to fill in these parameters, then they can inject special characters used in the encoding scheme to add or modify parameters. For example, if user input is fed directly into an HTTP GET request and the user provides the value "myInput&new_param=myValue", then the input parameter is set to myInput, but a new parameter (new_param) is also added with a value of myValue. This can significantly change the meaning of the query that is processed by the server. Any encoding scheme where parameters are identified and separated by text characters is potentially vulnerable to this attack - the HTTP GET encoding used above is just one example.
Flash Parameter Injection CAPEC-174 An adversary takes advantage of improper data validation to inject malicious global parameters into a Flash file embedded within an HTML document. Flash files can leverage user-submitted data to configure the Flash document and access the embedding HTML document.
Using Meta-characters in E-mail Headers to Inject Malicious Payloads CAPEC-41 This type of attack involves an attacker leveraging meta-characters in email headers to inject improper behavior into email programs. Email software has become increasingly sophisticated and feature-rich. In addition, email applications are ubiquitous and connected directly to the Web making them ideal targets to launch and propagate attacks. As the user demand for new functionality in email applications grows, they become more like browsers with complex rendering and plug in routines. As more email functionality is included and abstracted from the user, this creates opportunities for attackers. Virtually all email applications do not list email header information by default, however the email header contains valuable attacker vectors for the attacker to exploit particularly if the behavior of the email client application is known. Meta-characters are hidden from the user, but can contain scripts, enumerations, probes, and other attacks against the user's system.
HTTP Parameter Pollution (HPP) CAPEC-460 An adversary adds duplicate HTTP GET/POST parameters by injecting query string delimiters. Via HPP it may be possible to override existing hardcoded HTTP parameters, modify the application behaviors, access and, potentially exploit, uncontrollable variables, and bypass input validation checkpoints and WAF rules.
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-python:0.2.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.2.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.2.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.2.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.2.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.2.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.4:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.3.4:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.4.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:0.5.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.0.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.0.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.4:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.4:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.5:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.5:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.6:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.6:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.7:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.7:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.8:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.8:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.9:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.9:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.10:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.10:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.11:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.11:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.12:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.12:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.13:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.1.13:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.2.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.3.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.5.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.5.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:1.6.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.2:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.3:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.5:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.5:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.6:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.6:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.7:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.7:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.8:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.8:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.9:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.9:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.10:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.10:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.13:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.13:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.14:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.14:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.15:*:*:*:*:*:*:*
cpe:2.3:a:codecov:codecov-python:2.0.15:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-10800: 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-4520 – The Uncanny Automator plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on multiple AJAX fu...
CVE-2025-3623 – The Uncanny Automator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.4.0.1 via deserialization ...
CVE-2025-4574 – In crossbeam-channel rust crate, the internal `Channel` type's `Drop` method has a race condition which could, in some circumstances, lead to a dou...
CVE-2025-47905 – Varnish Cache before 7.6.3 and 7.7 before 7.7.1, and Varnish Enterprise before 6.0.13r14, allow client-side desync via HTTP/1 requests, because the...
CVE-2025-26646 – External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing o...