Openmoney API up to 2020-06-29 Javascript Math.random entropy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Openmoney API up to 2020-06-29 and classified as problematic. Affected by this issue is the function Math.random of the component Javascript Handler. The manipulation leads to entropy.
This vulnerability is uniquely identified as CVE-2022-30782. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in Openmoney API up to 2020-06-29 (Automation Software). This issue affects the function Math.random of the component Javascript Handler. The manipulation with an unknown input leads to a entropy vulnerability. Using CWE to declare the problem leads to CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. Impacted is confidentiality.
The weakness was disclosed 05/16/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-30782 since 05/16/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.6
VulDB Temp Score: 2.6
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: EntropyCWE: CWE-332 / CWE-331 / CWE-330
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/16/2022 🔍05/16/2022 🔍
05/16/2022 🔍
05/18/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-30782 (🔍)
GCVE (CVE): GCVE-0-2022-30782
GCVE (VulDB): GCVE-100-199937
Entry
Created: 05/16/2022 13:24Updated: 05/18/2022 09:20
Changes: 05/16/2022 13:24 (39), 05/18/2022 09:20 (1)
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.