# CVE-2022-41387: Supply chain in n/a

> A backdoor in the d8s-pdfs Python package allows attackers to execute arbitrary code via a malicious dependency.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-8xw6-jxhp-pcmc, PYSEC-2022-43029, PYSEC-2022-43050

## What is CVE-2022-41387?

CVE-2022-41387 is a critical vulnerability in n/a, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-41387?

2 open source packages ship an affected version, including d8s-pdfs and democritus-urls. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `d8s-pdfs` | PyPI | All versions | None |
| `democritus-urls` | PyPI | All versions | None |

Products: Democritus D8s-Pdfs.

## How do I fix CVE-2022-41387?

No fix has been published for CVE-2022-41387 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41387 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41387 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41387 and fix it if it is affected.

What it is: CVE-2022-41387 is a critical vulnerability in n/a, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41387 exists.

Affected packages and fixed versions:
- d8s-pdfs (PyPI): affected all versions; no fix listed
- democritus-urls (PyPI): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41387/ (Markdown: https://insights.sbomify.com/CVE-2022-41387/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41387
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41387
- OSV: https://osv.dev/vulnerability/CVE-2022-41387

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41387/
Summaries are generated and may contain mistakes; the official description above is the record.