CVE-2020-13129
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 the stashcat app through 3.9.1 for macOS, Windows, Android, iOS, and possibly other platforms. The GET method is used with client_key and device_id data in the query string, which allows attackers to obtain sensitive information by reading web-server logs.
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 · high confidenceThe stashcat app transmits sensitive authentication credentials (client_key and device_id) in URL query strings using the GET HTTP method. These credentials are then logged by web servers, allowing attackers who gain access to server logs to obtain these session/device identifiers and potentially impersonate users.
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<= 3.9.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Confirm Stashcat installation and versionLocate the Heinekingmedia Stashcat application on your system or mobile device, then check the installed version number in the app's about section, settings, or system app manager.Affected if The installed version is 3.9.1 or lower.
-
Inspect network traffic for credential transmissionSet up a network proxy (such as Burp Suite, Charles Proxy, or mitmproxy) to intercept HTTP traffic from the Stashcat app. Trigger authentication events such as login or session renewal, then examine the request method and URL for each authenticated request.Affected if Any HTTP request to the Stashcat server uses the GET method with client_key or device_id appearing as URL query string parameters.
-
Examine web server access logsObtain access logs from the Stashcat backend server or any reverse proxy/log aggregation system. Search for entries containing the query parameters 'client_key' or 'device_id' in the requested URLs.Affected if Server logs contain entries with 'client_key' or 'device_id' values appearing in the URL query string portion of GET requests.
-
Verify authentication endpoint configurationReview the Stashcat application's network configuration or API documentation to identify authentication endpoints. Check whether these endpoints are configured to accept credentials via GET request parameters rather than POST body or headers.Affected if Authentication endpoints accept credentials via URL query parameters in GET requests.
You are affected if Stashcat version is 3.9.1 or lower AND credentials (client_key/device_id) are transmitted via GET requests in URL query strings, which would be visible in server logs.
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 dataMigrate sensitive credential transmission from GET requests with query parameters to POST requests with data in the request body or headers, and implement server-side log sanitization to exclude sensitive parameters.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13129 — 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-2020-13129 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