{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-2263 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-2263 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2263 is a low-severity vulnerability in n/a, published on 23 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-2263 and fix it if it is affected.\n\nWhat it is: CVE-2015-2263 is a low-severity vulnerability in n/a, published on 23 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-2263 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-2015-2263/ (Markdown: https://insights.sbomify.com/CVE-2015-2263/index.md)","id":"CVE-2015-2263","markdown":"https://insights.sbomify.com/CVE-2015-2263/index.md","name":"CVE-2015-2263","record":{"aliases":["GHSA-6whv-hjxj-235c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cloudera Manager","requires_auth":"low_privilege","summary":"Local attackers can read sensitive configuration files due to global read permissions, exposing keys and credentials.","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":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Cloudera Manager 4.x, 5.0.x before 5.0.6, 5.1.x before 5.1.5, 5.2.x before 5.2.5, and 5.3.x before 5.3.3 uses global read permissions for files in its configuration directory when starting YARN NodeManager, which allows local users to obtain sensitive information by reading the files, as demonstrated by yarn.keytab or ssl-server.xml in /var/run/cloudera-scm-agent/process.","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-2015-2263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2015-2264"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2015-2255"},"products":["n/a"],"published":"2017-03-23","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":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-9326","kev_date_added":null,"published":"2019-07-03"},{"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-06","vendors":["n/a"]},"summary":"Local attackers can read sensitive configuration files due to global read permissions, exposing keys and credentials.","url":"https://insights.sbomify.com/CVE-2015-2263/"}