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

> A backdoor in the d8s-python library allows attackers to execute arbitrary code via a compromised 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:** 7 Nov 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-3hp7-g25q-23p8

## What is CVE-2022-44049?

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

### Official description

The d8s-python for python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. A potential code execution backdoor inserted by third parties is the democritus-grammars package. The affected version of d8s-htm is 0.1.0.

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

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

It affects 1 product.


Products: Democritus D8s-Python.

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

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

## Is CVE-2022-44049 being exploited?

There is no known exploitation of CVE-2022-44049 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-43305](https://insights.sbomify.com/CVE-2022-43305/): Supply chain in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44049 is a critical vulnerability in n/a, published on 7 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-44049 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-44049/ (Markdown: https://insights.sbomify.com/CVE-2022-44049/index.md)
```

## Sources

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

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