dbcve.org
D8s TimerApplication · Democritus

CVE-2022-43304

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-timer 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-uuids 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 attack where the democritus-uuids package (a third-party dependency) contains an inserted code execution backdoor. The d8s-timer and d8s-htm Python packages distributed on PyPI incorporate this compromised dependency, allowing arbitrary code execution by the attacker.

MitigationImmediately remove/uninstall the affected d8s-timer and d8s-htm packages from all environments, conduct forensic audit for unauthorized access or code execution, and replace with secure alternatives or alternative packages.

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 TimerApplication
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-timer package is installed
    Run `pip show d8s-timer` or `pip list | grep d8s-timer` to see if the package is present in your environment
    Affected if d8s-timer version 0.1.0 is installed
  2. Check if d8s-htm package is installed
    Run `pip show d8s-htm` or `pip list | grep d8s-htm` to see if the package is present in your environment
    Affected if d8s-htm package is installed (any version that depends on the compromised democritus-uuids)
  3. Check for democritus-uuids dependency
    Run `pip show d8s-timer` or `pip show d8s-htm` to view their dependencies, or run `pipdeptree | grep democritus-uuids` to trace the dependency chain
    Affected if democritus-uuids is listed as a dependency
  4. Verify package versions
    Compare the installed versions of d8s-timer (should show 0.1.0) and d8s-htm against the affected version range
    Affected if d8s-timer version 0.1.0 is confirmed installed

Your environment is affected if d8s-timer version 0.1.0 or d8s-htm with the compromised democritus-uuids dependency is installed, as either allows the attacker-supplied code execution backdoor to run.

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/uninstall the affected d8s-timer and d8s-htm packages from all environments, conduct forensic audit for unauthorized access or code execution, and replace with secure alternatives or alternative packages.

Recommended fix Low confidence

A version of d8s-timer greater than 0.1.0 (check PyPI for current available versions; if none safe exist, use an alternative timer library)

  1. 1. Check your project's requirements.txt, setup.py, or pyproject.toml for any dependency on d8s-timer version 0.1.0
  2. 2. If d8s-timer is directly or indirectly (via democritus-uuids) used in your project, remove or replace it immediately
  3. 3. Search PyPI for the current version of d8s-timer to determine if a safe, patched version is available
  4. 4. If a fixed version exists (version > 0.1.0), upgrade to it: pip install d8s-timer==<fixed_version>
  5. 5. If no safe version is available, remove d8s-timer from your dependencies and find an alternative timer/UUID library
  6. 6. Audit your environment for any malicious code execution: review any files or processes that may have been created by the compromised package
  7. 7. Rebuild and redeploy your application in a clean environment
Caveat If upgrading to a newer version, review API changes; if removing the package entirely, refactor code that depends on d8s-timer

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

Fix this in D8s Timer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43304 — 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-43304 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