StashCat up to 3.9.2 Database File cleartext storage

Summaryinfo

A vulnerability, which was classified as critical, has been found in StashCat up to 3.9.2. This affects an unknown function of the component Database File. The manipulation leads to cleartext storage. This vulnerability is uniquely identified as CVE-2020-13637. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability was found in StashCat up to 3.9.2 and classified as problematic. This issue affects an unknown functionality of the component Database File. The manipulation with an unknown input leads to a cleartext storage vulnerability. Using CWE to declare the problem leads to CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. Impacted is confidentiality. The summary by CVE is:

An issue was discovered in the stashcat app through 3.9.2 for macOS, Windows, Android, iOS, and possibly other platforms. It stores the client_key, the device_id, and the public key for end-to-end encryption in cleartext, enabling an attacker (by copying or having access to the local storage database file) to login to the system from any other computer, and get unlimited access to all data in the users's context.

The weakness was disclosed 06/17/2020. The identification of this vulnerability is CVE-2020-13637 since 05/27/2020. An attack has to be approached locally. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1555 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.

Productinfo

Name

• StashCat

Version

• 3.9.0
• 3.9.1
• 3.9.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion