# CVE-2017-11129: Hardcoded credentials in n/a

> Attackers with keystore access can read sensitive data like private keys due to a hard-coded password in the StashCat Android application.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5473-97w5-63g9

## What is CVE-2017-11129?

CVE-2017-11129 is a critical vulnerability in n/a, published on 1 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in heinekingmedia StashCat through 1.7.5 for Android. The keystore is locked with a hard-coded password. Therefore, everyone with access to the keystore can read the content out, for example the private key of the user.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2017-11129?

It affects 1 product.


Products: Stashcat Heinekingmedia.

## How do I fix CVE-2017-11129?

No fix has been published for CVE-2017-11129 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11129 being exploited?

There is no known exploitation of CVE-2017-11129 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-11130](https://insights.sbomify.com/CVE-2017-11130/): Other in n/a (high 8.1)
- [CVE-2017-11133](https://insights.sbomify.com/CVE-2017-11133/): Weak cryptography in n/a (high 7.5)
- [CVE-2017-11135](https://insights.sbomify.com/CVE-2017-11135/): Missing authorization in n/a (high 7.5)
- [CVE-2017-11134](https://insights.sbomify.com/CVE-2017-11134/): Information disclosure in n/a (medium 6.5)
- [CVE-2017-11136](https://insights.sbomify.com/CVE-2017-11136/): Weak cryptography in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11129 and fix it if it is affected.

What it is: CVE-2017-11129 is a critical vulnerability in n/a, published on 1 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11129 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11129/ (Markdown: https://insights.sbomify.com/CVE-2017-11129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11129
- OSV: https://osv.dev/vulnerability/CVE-2017-11129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11129/
Summaries are generated and may contain mistakes; the official description above is the record.