PuddingBot up to 0.0.6-b933652 main.py hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in PuddingBot up to 0.0.6-b933652. This issue affects some unknown processing of the file main.py. Executing a manipulation can lead to hard-coded credentials. This vulnerability appears as CVE-2022-21669. The attacker needs to be present on the local network. There is no available exploit.
Details
A vulnerability classified as critical was found in PuddingBot up to 0.0.6-b933652. This vulnerability affects an unknown part of the file main.py. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 01/11/2022 as GHSA-cxgr-xpmj-9qjm. The advisory is available at github.com. This vulnerability was named CVE-2022-21669 since 11/16/2021. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1110.001 by the MITRE ATT&CK project.
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-26884). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (GitHub, Inc.): 🔍
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
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
11/16/2021 🔍01/11/2022 🔍
01/11/2022 🔍
04/27/2026 🔍
Sources
Advisory: GHSA-cxgr-xpmj-9qjmStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2022-21669 (🔍)
GCVE (CVE): GCVE-0-2022-21669
GCVE (VulDB): GCVE-100-190018
EUVD: 🔍
Entry
Created: 01/11/2022 18:47Updated: 04/27/2026 14:47
Changes: 01/11/2022 18:47 (47), 01/13/2022 14:39 (2), 04/27/2026 14:47 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.