| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in totd up to 1.5.2. The impacted element is an unknown function of the component Mesg ID Handler. This manipulation causes random values. This vulnerability is handled as CVE-2022-34295. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in totd up to 1.5.2. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Mesg ID Handler. The manipulation with an unknown input leads to a random values vulnerability. The CWE definition for the vulnerability is CWE-330. The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. As an impact it is known to affect confidentiality. The summary by CVE is:
totd before 1.5.3 does not properly randomize mesg IDs.
The weakness was released 06/24/2022 as afd8a10a6a21f82a70940d1b43cff48143250399. The advisory is shared at github.com. This vulnerability is known as CVE-2022-34295 since 06/22/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Upgrading to version 1.5.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch afd8a10a6a21f82a70940d1b43cff48143250399 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Random valuesCWE: CWE-330 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: totd 1.5.3
Patch: afd8a10a6a21f82a70940d1b43cff48143250399
Timeline
06/22/2022 🔍06/24/2022 🔍
06/24/2022 🔍
06/24/2022 🔍
Sources
Advisory: afd8a10a6a21f82a70940d1b43cff48143250399Status: Confirmed
CVE: CVE-2022-34295 (🔍)
GCVE (CVE): GCVE-0-2022-34295
GCVE (VulDB): GCVE-100-202561
Entry
Created: 06/24/2022 06:56Changes: 06/24/2022 06:56 (22), 06/24/2022 06:57 (21)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.