CVE-2017-11136

Description

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.

6.5

CVSS

Severity: Medium

CVSS 3.0 •

CVSS 2.0 •

EPSS 0.14%

Third-Party Advisory seclists.org

Affected: n/a n/a

References

Link	Tags
http://seclists.org/fulldisclosure/2017/Jul/90	third party advisory mailing list

Frequently Asked Questions

What is the severity of CVE-2017-11136?: CVE-2017-11136 has been scored as a medium severity vulnerability.
How to fix CVE-2017-11136?: To fix CVE-2017-11136, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-11136 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2017-11136 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.