CVE-2017-11136

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.

Published: 2017-08-01 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-11136 is rated Moderate Risk (40/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.50%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-11136

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.14% 0.50% +0.36%
2 2025-03-30 0.28% 0.14% -0.14%
3 2025-03-29 — 0.28% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-11136

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
4.0 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 2.9 [email protected]

Weakness enumeration for CVE-2017-11136

Affected software / configurations for CVE-2017-11136

Vendor Product Version Raw CPE
stashcat heinekingmedia <= 1.7.5 cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:*:android:*:*
stashcat heinekingmedia <= 0.0.80w cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:web:*:*:*
stashcat heinekingmedia <= 0.0.86w cpe:2.3:a:stashcat:heinekingmedia:*:*:*:*:desktop:*:*:*

References for CVE-2017-11136

URL Tags
http://seclists.org/fulldisclosure/2017/Jul/90 Mailing List Third Party Advisory
cvelogic Threat Intelligence