StashCat on Android Backend Database Stored key management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.7$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in StashCat on Android. Affected by this vulnerability is an unknown functionality of the component Backend Database. Such manipulation leads to key management (Stored). This vulnerability is referenced as CVE-2017-11136. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in StashCat on Android (Android App Software) (version unknown) and classified as problematic. Affected by this issue is an unknown function of the component Backend Database. The manipulation with an unknown input leads to a key management vulnerability (Stored). Using CWE to declare the problem leads to CWE-320. Impacted is confidentiality, integrity, and availability. CVE summarizes:

An issue was discovered in heinekingmedia StashCat through 1.7.5 for Android, through 0.0.80w for Web, and through 0.0.86 for Desktop. It uses RSA to exchange a secret for symmetric encryption of messages. However, the private RSA key is not only stored on the client but transmitted to the backend, too. Moreover, the key to decrypt the private key is composed of the first 32 bytes of the SHA-512 hash of the user password. But this hash is stored on the backend, too. Therefore, everyone with access to the backend database can read the transmitted secret for symmetric encryption, hence can read the communication.

The bug was discovered 07/31/2017. The weakness was published 08/01/2017 (Website). The advisory is shared for download at seclists.org. This vulnerability is handled as CVE-2017-11136 since 07/09/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Similar entries are available at VDB-104713, VDB-104714, VDB-104715 and VDB-104716. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Stored
Class: Key management / Stored
CWE: CWE-320
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/09/2017 🔍
07/31/2017 +22 days 🔍
08/01/2017 +1 days 🔍
08/01/2017 +0 days 🔍
08/02/2017 +1 days 🔍
11/02/2019 +822 days 🔍

Sourcesinfo

Advisory: seclists.org
Status: Not defined

CVE: CVE-2017-11136 (🔍)
GCVE (CVE): GCVE-0-2017-11136
GCVE (VulDB): GCVE-100-104720
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍

Entryinfo

Created: 08/02/2017 11:11
Updated: 11/02/2019 20:27
Changes: 08/02/2017 11:11 (59), 11/02/2019 20:27 (1)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!