CVE-2019-10800: Command Injection

Published Jul 13, 2022
·
Updated

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.

Affected Software

2 affected componentsFixes available
pip/codecov<2.0.16
2.0.16
Codecov Codecov-python<2.0.16

Event History

Jul 13, 2022
CVE Published
via MITRE·11:50 AM
Data Sourced
via MITRE·11:50 AM
DescriptionSeverityWeakness
Jul 14, 2022
Advisory Published
via GitHub·12:00 AM

Frequently Asked Questions

1

What is the severity of CVE-2019-10800?

CVE-2019-10800 is classified as a moderate severity vulnerability due to its potential impact on system integrity.

2

How do I fix CVE-2019-10800?

To remediate CVE-2019-10800, update the codecov package to version 2.0.16 or higher.

3

What software is affected by CVE-2019-10800?

CVE-2019-10800 affects the codecov package versions prior to 2.0.16.

4

What is the nature of CVE-2019-10800 vulnerability?

CVE-2019-10800 is caused by improper sanitization of gcov arguments before they are passed to the popen method.

5

Is CVE-2019-10800 exploitable?

Yes, CVE-2019-10800 can be exploited to execute arbitrary code in the context of the vulnerable application.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203