What is the severity of CVE-2022-42036?

CVE-2022-42036 has a high severity due to the potential for code execution from a backdoor.

How do I fix CVE-2022-42036?

To fix CVE-2022-42036, upgrade to a secure version of the d8s-urls package that does not include the backdoor.

What versions of d8s-urls are affected by CVE-2022-42036?

CVE-2022-42036 affects version 0.1.0 of the d8s-urls package.

What is the primary risk associated with CVE-2022-42036?

The primary risk of CVE-2022-42036 is unauthorized remote code execution through the backdoor in the affected package.

Who is responsible for the vulnerability in CVE-2022-42036?

CVE-2022-42036 was introduced by a third party who inserted a backdoor into the democritus-csv package.

Vulnerability/
CVE-2022-42036

critical

9.8

CWE

434

11/10/2022

3/8/2024

CVE-2022-42036: Malicious File Upload

First published: Tue Oct 11 2022(Updated: )

The d8s-urls package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. The backdoor is the democritus-csv package. The affected version is 0.1.0.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Democritus Urls Project	=0.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-42036?
CVE-2022-42036 has a high severity due to the potential for code execution from a backdoor.
How do I fix CVE-2022-42036?
To fix CVE-2022-42036, upgrade to a secure version of the d8s-urls package that does not include the backdoor.
What versions of d8s-urls are affected by CVE-2022-42036?
CVE-2022-42036 affects version 0.1.0 of the d8s-urls package.
What is the primary risk associated with CVE-2022-42036?
The primary risk of CVE-2022-42036 is unauthorized remote code execution through the backdoor in the affected package.
Who is responsible for the vulnerability in CVE-2022-42036?
CVE-2022-42036 was introduced by a third party who inserted a backdoor into the democritus-csv package.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/author
agent/weakness
agent/last-modified-date
agent/first-publish-date
agent/event
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/democritus
canonical/democritus urls project
version/democritus urls project/0.1.0

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2022-42036?
CVE-2022-42036 has a high severity due to the potential for code execution from a backdoor.
How do I fix CVE-2022-42036?
To fix CVE-2022-42036, upgrade to a secure version of the d8s-urls package that does not include the backdoor.
What versions of d8s-urls are affected by CVE-2022-42036?
CVE-2022-42036 affects version 0.1.0 of the d8s-urls package.
What is the primary risk associated with CVE-2022-42036?
The primary risk of CVE-2022-42036 is unauthorized remote code execution through the backdoor in the affected package.
Who is responsible for the vulnerability in CVE-2022-42036?
CVE-2022-42036 was introduced by a third party who inserted a backdoor into the democritus-csv package.