| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in d8s-timer 0.1.0 on Python. It has been classified as critical. The affected element is an unknown function. This manipulation causes backdoor. This vulnerability appears as CVE-2022-43304. There is no available exploit.
Details
A vulnerability has been found in d8s-timer 0.1.0 on Python and classified as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a backdoor vulnerability. The CWE definition for the vulnerability is CWE-912. The product contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented 11/07/2022. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2022-43304 since 10/17/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1588.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-0381). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: BackdoorCWE: CWE-912
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/17/2022 🔍11/07/2022 🔍
11/07/2022 🔍
03/09/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-43304 (🔍)
GCVE (CVE): GCVE-0-2022-43304
GCVE (VulDB): GCVE-100-213043
EUVD: 🔍
Entry
Created: 11/07/2022 21:51Updated: 03/09/2026 16:30
Changes: 11/07/2022 21:51 (37), 12/05/2022 09:13 (12), 03/09/2026 16:30 (16)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.