CVE-2017-11135

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. The logout mechanism does not check for authorization. Therefore, an attacker only needs to know the device ID. This causes a denial of service. This might be interpreted as a vulnerability in customer-controlled software, in the sense that the StashCat client side has no secure way to signal that it is ending a session and that data should be deleted.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.30%
Third-Party Advisory seclists.org
Affected: n/a n/a
Published at:
Updated at:

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-11135?
CVE-2017-11135 has been scored as a high severity vulnerability.
How to fix CVE-2017-11135?
To fix CVE-2017-11135, 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-11135 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-11135 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.
© 2025 Under My Watch. All Rights Reserved.