D8s DatesApplication · Democritus
CVE-2022-44052
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 · uneditedThe d8s-dates 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-timezones 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 · high confidenceThe d8s-dates Python package (and related d8s-htm v0.1.0) distributed via PyPI contained a malicious code execution backdoor via a trojanized dependency - the democritus-timezones package. This supply chain compromise allowed arbitrary code execution by threat actors who compromised the third-party package.
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 DatesApplication
= 0.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if d8s-dates is installedRun `pip show d8s-dates` or `pip list | grep d8s-dates` to see if the package is present in your Python environmentAffected if d8s-dates version 0.1.0 is installed
-
Check if d8s-htm is installedRun `pip show d8s-htm` or `pip list | grep d8s-htm` to verify if this related package exists in your environmentAffected if d8s-htm version 0.1.0 is installed
-
Verify installed package versionsReview the version number shown in the pip output. Compare against the affected version 0.1.0 for both d8s-dates and d8s-htmAffected if Either package shows version 0.1.0
-
Check for the malicious democritus-timezones dependencyRun `pip show d8s-dates` to inspect the dependencies listed under 'Requires' or use `pip list | grep democritus` to see if the compromised democritus-timezones package is presentAffected if The democritus-timezones package appears as a dependency or is installed separately
Your environment is affected if d8s-dates or d8s-htm version 0.1.0 is installed, particularly if the democritus-timezones dependency is present, as this indicates exposure to the supply chain backdoor.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately remove d8s-dates and d8s-htm v0.1.0 from any environment where they were installed. Audit systems for unauthorized access or code execution that may have occurred via this backdoor, and rebuild or reseed any compromised environments as a precaution.
Fix this in D8s Dates
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44052 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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