codecov up to 2.0.15 popen privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

Summaryinfo

A vulnerability was found in codecov up to 2.0.15. It has been classified as problematic. This impacts the function popen. Performing a manipulation results in an unknown weakness. This vulnerability is reported as CVE-2019-10800. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in codecov up to 2.0.15. The impact remains unknown. The summary by CVE is:

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.

The weakness was disclosed 07/13/2022 as 2a80aa434f74feb31242b6f213b75ce63ae97902. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-10800 since 04/03/2019. Technical details are known, but no exploit is available.

Upgrading to version 2.0.16 eliminates this vulnerability. Applying the patch 2a80aa434f74feb31242b6f213b75ce63ae97902 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.0
VulDB Meta Temp Score: 5.9

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (Snyk): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: codecov 2.0.16
Patch: 2a80aa434f74feb31242b6f213b75ce63ae97902

Timelineinfo

04/03/2019 🔍
07/13/2022 +1197 days 🔍
07/13/2022 +0 days 🔍
07/23/2022 +10 days 🔍

Sourcesinfo

Advisory: 2a80aa434f74feb31242b6f213b75ce63ae97902
Status: Confirmed

CVE: CVE-2019-10800 (🔍)
GCVE (CVE): GCVE-0-2019-10800
GCVE (VulDB): GCVE-100-203817

Entryinfo

Created: 07/13/2022 16:27
Updated: 07/23/2022 11:15
Changes: 07/13/2022 16:27 (40), 07/23/2022 11:15 (12)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!