{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9326 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9326 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9326 is a high-severity vulnerability in n/a, published on 3 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9326 and fix it if it is affected.\n\nWhat it is: CVE-2017-9326 is a high-severity vulnerability in n/a, published on 3 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-9326 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-9326/ (Markdown: https://insights.sbomify.com/CVE-2017-9326/index.md)","id":"CVE-2017-9326","markdown":"https://insights.sbomify.com/CVE-2017-9326/index.md","name":"CVE-2017-9326","record":{"aliases":["GHSA-4xqw-hr8p-jvp5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloudera Manager","requires_auth":"low_privilege","summary":"Attackers can read the Spark History Server keystore password from unsecured files in Cloudera Manager directories, potentially compromising secure communications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cloudera_manager","vendor":"cloudera"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"The keystore password for the Spark History Server may be exposed in unsecured files under the /var/run/cloudera-scm-agent directory managed by Cloudera Manager. The keystore file itself is not exposed.","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":"Information disclosure in n/a","id":"CVE-2017-9326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-9327"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2017-9325"},"products":["n/a"],"published":"2019-07-03","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-30132","kev_date_added":null,"published":"2021-11-08"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-7399","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2018-11744","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-6495","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2016-3192","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2017-9327","kev_date_added":null,"published":"2019-07-03"}],"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 read the Spark History Server keystore password from unsecured files in Cloudera Manager directories, potentially compromising secure communications.","url":"https://insights.sbomify.com/CVE-2017-9326/"}