LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43306: The d8s-timer for python, as distributed on PyPI, included a potential code-execution backdoor inserted by...

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-dates package. The affected version of d8s-htm is 0.1.0.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a Python package supply-chain risk: the public record reports a potential code-execution backdoor involving d8s-timer and democritus-dates on PyPI. The record is internally inconsistent about the exact affected package/version, so treat exposure analysis as urgent but evidence-limited.

Executive priority

Prioritize this as a high-severity supply-chain review. The business risk is credential theft or code execution through a dependency, but the public evidence does not confirm active exploitation or a specific remediation path.

Technical view

The CVE assigns CVSS 8.8 and CWE-434 to a potential third-party backdoor in PyPI-distributed packages. Sources name d8s-timer and democritus-dates, while the description also says d8s-htm 0.1.0. No CPEs, fixed version, or vendor mitigation are provided in the bundle.

Likely exposure

Organizations may be exposed if Python projects, lockfiles, build systems, containers, or artifact caches included d8s-timer, democritus-dates, or the referenced d8s-htm 0.1.0 package. Exposure depends on package installation, not network reachability.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk comes from possible execution of malicious package code during installation, import, build, or runtime, depending on how the package was used.

Researcher notes

Key limitation: the record names multiple packages inconsistently and provides no CPEs or fixed version. Validate against PyPI metadata and the linked GitHub issue before making product-specific claims.

Mitigation direction

  • Check vendor and PyPI guidance for package status and safe versions.
  • Remove affected packages from dependencies if not strictly required.
  • Rebuild environments from trusted lockfiles after dependency removal.
  • Rotate credentials exposed to affected build or runtime environments.
  • Review package indexes and mirrors for cached affected artifacts.

Validation and detection

  • Search dependency manifests and lockfiles for d8s-timer and democritus-dates.
  • Check artifact caches, containers, and CI logs for package installation evidence.
  • Review SBOMs for the named packages and d8s-htm 0.1.0.
  • Inspect affected hosts for unexpected Python package files or imports.
  • Confirm no secrets were available to impacted build jobs.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-43306 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-43306Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.