{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11129 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2017-11129 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2017-11129 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-11129/ (Markdown: https://insights.sbomify.com/CVE-2017-11129/index.md)","id":"CVE-2017-11129","markdown":"https://insights.sbomify.com/CVE-2017-11129/index.md","name":"CVE-2017-11129","record":{"aliases":["GHSA-5473-97w5-63g9"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Android StashCat app","requires_auth":"none","summary":"Attackers with keystore access can read sensitive data like private keys due to a hard-coded password in the StashCat Android application.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"heinekingmedia","vendor":"stashcat"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-11129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2017-11130"},"packages":[],"prev":{"headline":"Bolt stored Cross-site Scripting (XSS)","id":"CVE-2017-11128"},"products":["n/a"],"published":"2017-08-01","related":[{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2017-11130","kev_date_added":null,"published":"2017-08-01"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2017-11133","kev_date_added":null,"published":"2017-08-01"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2017-11135","kev_date_added":null,"published":"2017-08-01"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2017-11134","kev_date_added":null,"published":"2017-08-01"},{"cvss_score":6.5,"headline":"Weak cryptography in n/a","id":"CVE-2017-11136","kev_date_added":null,"published":"2017-08-01"},{"cvss_score":5.9,"headline":"Weak cryptography in n/a","id":"CVE-2017-11131","kev_date_added":null,"published":"2017-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with keystore access can read sensitive data like private keys due to a hard-coded password in the StashCat Android application.","url":"https://insights.sbomify.com/CVE-2017-11129/"}