Shenzhen Yunding Oclean App 2.1.2 on Android hard-coded key
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Shenzhen Yunding Oclean App 2.1.2 on Android. This affects an unknown part. The manipulation leads to hard-coded key. This vulnerability is uniquely identified as CVE-2020-25493. It is possible to initiate the attack remotely. There is no exploit available. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in Shenzhen Yunding Oclean App 2.1.2 on Android (Android App Software). It has been rated as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a hard-coded key vulnerability. Using CWE to declare the problem leads to CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. Impacted is confidentiality.
The weakness was shared 02/12/2021. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2020-25493. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.
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
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔍
ATT&CK: 🔍
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
09/14/2020 🔍02/12/2021 🔍
02/12/2021 🔍
02/28/2021 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-25493 (🔍)
GCVE (CVE): GCVE-0-2020-25493
GCVE (VulDB): GCVE-100-169784
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 02/12/2021 09:23Updated: 02/28/2021 10:14
Changes: 02/12/2021 09:23 (37), 02/28/2021 10:07 (2), 02/28/2021 10:14 (18)
Complete: 🔍
Cache ID: 216:916:103
No comments yet. Languages: en.
Please log in to comment.