CVE-2017-11135
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe logout mechanism in StashCat across Android, Web, and Desktop versions lacks authorization validation. An attacker only needs a valid device ID to send a logout request, which forcibly terminates a user's session and causes denial of service. The vulnerability stems from the server trusting client-provided device IDs without verifying the requester's identity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.7.5<= 0.0.80w<= 0.0.86wCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify StashCat server versionCheck the installed version of the StashCat server software running in your environment. Consult server documentation, check software inventory, or query the server's version endpoint if available.Affected if The running server version is 1.7.5 or earlier for Android deployments, 0.0.80w or earlier for web deployments, or 0.0.86w or earlier for desktop deployments.
-
Inspect logout endpoint authentication requirementsReview server configuration or API documentation for the logout endpoint. Examine whether the endpoint accepts a device ID parameter and whether it requires a valid session token or credentials in addition to the device ID.Affected if The logout endpoint accepts and processes logout requests using only a device ID without requiring a valid session token, API key, or other credential-based authentication.
-
Test logout endpoint behaviorIf you have a test environment, send a logout request with only a valid device ID (no session token or credentials) to the logout endpoint and observe whether the session is terminated.Affected if The server processes the logout request and terminates the session when given only a device ID without any session authentication.
-
Check for missing CSRF protectionReview whether the logout endpoint implements CSRF tokens or origin validation to prevent cross-site request forgery attacks.Affected if The logout endpoint lacks CSRF protections such as token validation or origin checking.
Your environment is affected if the StashCat server version is at or below 1.7.5, 0.0.80w, or 0.0.86w, or if the logout endpoint accepts device IDs alone without requiring valid session authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper session authentication on the logout endpoint - require valid session tokens or credentials rather than relying solely on device IDs to authorize logout requests. Additionally, implement rate limiting and CSRF protections.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-11135 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data