CVE-2017-11136 Weak cryptography in n/a
Attackers with backend database access can decrypt user communications because private keys and password hashes are improperly stored on the server.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-11136?
CVE-2017-11136 is a medium-severity vulnerability in n/a, published on 1 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2017-11136?
It affects 1 product.
Products include Stashcat Heinekingmedia.
How do I fix CVE-2017-11136?
No fix has been published for CVE-2017-11136 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-11136 being exploited?
There is no known exploitation of CVE-2017-11136 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-cfr2-hjc5-vfvg.