{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11135 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11135 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11135 is a high-severity missing authorization 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-11135 and fix it if it is affected.\n\nWhat it is: CVE-2017-11135 is a high-severity missing authorization 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-11135 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-11135/ (Markdown: https://insights.sbomify.com/CVE-2017-11135/index.md)","id":"CVE-2017-11135","markdown":"https://insights.sbomify.com/CVE-2017-11135/index.md","name":"CVE-2017-11135","record":{"aliases":["GHSA-w66g-jmw2-wqv9"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"StashCat client","requires_auth":"none","summary":"Attackers can force logout of StashCat users by knowing the device ID due to missing authorization checks, causing denial of service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"heinekingmedia","vendor":"stashcat"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","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":"Missing authorization in n/a","id":"CVE-2017-11135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2017-11136"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-11134"},"products":["n/a"],"published":"2017-08-01","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-11129","kev_date_added":null,"published":"2017-08-01"},{"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":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 can force logout of StashCat users by knowing the device ID due to missing authorization checks, causing denial of service.","url":"https://insights.sbomify.com/CVE-2017-11135/"}