LiveActive security incident?Get immediate response
CVE Record

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

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a suspected code-execution backdoor in Python packages distributed through PyPI. For executives, the concern is supply-chain compromise: installing a package could potentially run attacker-controlled code. The public record is sparse and internally inconsistent, so urgency is high for dependency review, not for assuming confirmed compromise everywhere.

Executive priority

Prioritize rapid inventory and containment. The potential impact is severe, but the public record is limited, so decisions should be based on whether the packages exist in your environment.

Technical view

CVE-2022-44048 reports a potential third-party code-execution backdoor involving d8s-urls and democritus-domains on PyPI. The description also mentions d8s-htm version 0.1.0, creating ambiguity. CVSS is 9.8, network exploitable, no privileges or user interaction required. No CPEs or precise affected product metadata are provided.

Likely exposure

Exposure is most likely in Python environments, CI systems, build images, or applications that directly or transitively installed the named PyPI packages. The provided affected metadata says n/a, so validation must rely on dependency inventories, lockfiles, SBOMs, and build records.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is supply-chain execution from a malicious or backdoored package, but public evidence here does not prove exploitation in the wild.

Researcher notes

The record has notable ambiguity: d8s-urls, democritus-domains, and d8s-htm 0.1.0 are all mentioned, while affected vendor/product fields are n/a. Avoid broad claims beyond these source names without additional vendor evidence.

Mitigation direction

  • Check PyPI and project guidance before selecting any replacement or safe version.
  • Remove or block the named packages until trust is established.
  • Review lockfiles and SBOMs for direct and transitive package references.
  • Rebuild affected environments from known-good dependency sources.
  • Treat privileged installations as possible incidents and follow internal response procedures.

Validation and detection

  • Search dependency manifests, lockfiles, SBOMs, and artifact metadata for the named packages.
  • Review CI and deployment logs for historical package installation evidence.
  • Identify systems where Python packages were installed with elevated privileges.
  • Confirm whether any internal package mirrors cached the referenced releases.
  • Document uncertainty caused by inconsistent package names in the CVE description.
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-44048 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-44048Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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.