Zizai Nut App Cloud API cache.db Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Zizai Nut App. The affected element is an unknown function of the file cache.db of the component Cloud API. This manipulation causes credentials management (Credentials). This vulnerability is registered as CVE-2016-6547. The attack needs to be launched locally. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Zizai Nut App (version now known). It has been declared as critical. Affected by this vulnerability is some unknown processing of the file cache.db of the component Cloud API. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). The CWE definition for the vulnerability is CWE-255. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The Zizai Tech Nut mobile app stores the account password used to authenticate to the cloud API in cleartext in the cache.db file.
The bug was discovered 10/24/2016. The weakness was published 07/13/2018 by Deral Heiland with Rapid7 (Website). It is possible to read the advisory at blog.rapid7.com. This vulnerability is known as CVE-2016-6547 since 08/03/2016. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 627 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93877†). Similar entries are available at VDB-121437 and VDB-121436. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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
Name: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
08/03/2016 🔍10/24/2016 🔍
10/25/2016 🔍
07/13/2018 🔍
07/13/2018 🔍
07/14/2018 🔍
12/27/2024 🔍
Sources
Advisory: blog.rapid7.comResearcher: Deral Heiland
Organization: Rapid7
Status: Confirmed
CVE: CVE-2016-6547 (🔍)
GCVE (CVE): GCVE-0-2016-6547
GCVE (VulDB): GCVE-100-121435
CERT: 🔍
SecurityFocus: 93877 - Zizai Tech Nut Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 07/14/2018 13:52Updated: 12/27/2024 05:01
Changes: 07/14/2018 13:52 (66), 03/04/2020 20:45 (1), 12/27/2024 05:01 (20)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.