dbcve.org
D8s PythonApplication · Democritus

CVE-2022-44049

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a supply chain compromise where third parties inserted a code-execution backdoor into Python packages (d8s-python and d8s-htm v0.1.0) distributed on PyPI. The backdoor was introduced through the democritus-grammars package, which was included as a dependency.

MitigationImmediately remove and avoid using d8s-python, d8s-htm v0.1.0, and any packages depending on democritus-grammars. Conduct a dependency audit to identify any affected packages in your environment and replace with alternative solutions or patched versions when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
D8s PythonApplication
Affected:= 0.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if d8s-python is installed
    Run `pip show d8s-python` or `pip list | grep d8s-python`
    Affected if d8s-python version 0.1.0 is installed
  2. Check if d8s-htm is installed
    Run `pip show d8s-htm` or `pip list | grep d8s-htm`
    Affected if d8s-htm version 0.1.0 is installed
  3. Check for democritus-grammars dependency
    Run `pip show democritus-grammars` or check the dependency tree with `pip list --format=freeze | grep democritus`
    Affected if democritus-grammars package is present in your environment
  4. Review dependency tree for affected packages
    Run `pipdeptree` or `pip freeze` to list all installed packages and search for d8s-python, d8s-htm, or democritus-grammars
    Affected if Any of these three packages appear in your dependency tree

Your environment is affected if d8s-python v0.1.0, d8s-htm v0.1.0, or democritus-grammars are present as dependencies, as they contain the malicious backdoor code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove and avoid using d8s-python, d8s-htm v0.1.0, and any packages depending on democritus-grammars. Conduct a dependency audit to identify any affected packages in your environment and replace with alternative solutions or patched versions when available.

Recommended fix Moderate confidence

Check PyPI for versions > 0.1.0 (safe version to be determined based on PyPI availability)

  1. 1. Immediately uninstall the compromised d8s-python version 0.1.0: pip uninstall d8s-python
  2. 2. Check if newer versions exist on PyPI that are not compromised: pip index versions d8s-python
  3. 3. If a safe version beyond 0.1.0 is available, install it: pip install d8s-python==<safe_version>
  4. 4. If no safe version exists, find an alternative package or wait for official confirmation of a clean release
  5. 5. Audit any systems that previously used the compromised package for potential compromise
  6. 6. Review dependencies of d8s-python (especially democritus-grammars) for similar compromises
Caveat If a fixed version exists, review changelog for any breaking changes; if no fixed version exists, migration to an alternative package may be required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in D8s Python Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44049 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data