Bluezone 1.0.0 React Native Bluetooth Scan random values ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical was found in Bluezone 1.0.0. This issue affects some unknown processing of the component React Native Bluetooth Scan. Executing a manipulation can lead to random values. This vulnerability appears as CVE-2020-12270. The attacker needs to be present on the local network. There is no available exploit. This vulnerability has historical importance owing to its background and reception. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability classified as critical was found in Bluezone 1.0.0. This vulnerability affects an unknown function of the component React Native Bluetooth Scan. 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, integrity, and availability. CVE summarizes:
React Native Bluetooth Scan in Bluezone 1.0.0 uses six-character alphanumeric IDs, which might make it easier for remote attackers to interfere with COVID-19 contact tracing by using many IDs.
The weakness was presented 04/27/2020. This vulnerability was named CVE-2020-12270 since 04/27/2020. The attack needs to approached within the local network. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 08/04/2024). This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project. This vulnerability has a historic impact due to its background and reception.
As 0-day the estimated underground price was around $25k-$100k. The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
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: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: 🔍
NVD Base Score: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/27/2020 🔍04/27/2020 🔍
04/27/2020 🔍
08/04/2024 🔍
Sources
Status: Not definedDisputed: 🔍
CVE: CVE-2020-12270 (🔍)
GCVE (CVE): GCVE-0-2020-12270
GCVE (VulDB): GCVE-100-154378
Entry
Created: 04/27/2020 08:53Updated: 08/04/2024 14:54
Changes: 04/27/2020 08:53 (36), 04/27/2020 08:58 (17), 08/04/2024 14:54 (18)
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.