{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8447 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8447 is a medium-severity vulnerability in Elastic X-Pack Security, published on 28 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8447 and fix it if it is affected.\n\nWhat it is: CVE-2017-8447 is a medium-severity vulnerability in Elastic X-Pack Security, published on 28 Sep 2017. 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-8447 in the wild and no public exploit code.\n\nAffected product: Elastic X-Pack Security. 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-8447/ (Markdown: https://insights.sbomify.com/CVE-2017-8447/index.md)","id":"CVE-2017-8447","markdown":"https://insights.sbomify.com/CVE-2017-8447/index.md","name":"CVE-2017-8447","record":{"aliases":["GHSA-gr96-2h6w-pf97"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic X-Pack Security","requires_auth":"low_privilege","summary":"Users with delete or index permissions can perform both actions, leading to privilege escalation and unauthorized data modification in Elastic clusters.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"x-pack","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"An error was found in the X-Pack Security 5.3.0 to 5.5.2 privilege enforcement. If a user has either 'delete' or 'index' permissions on an index in a cluster, they may be able to issue both delete and index requests against that index.","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":"Privilege escalation in Elastic X-Pack Security","id":"CVE-2017-8447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Elastic X-Pack Alerting","id":"CVE-2017-8448"},"packages":[],"prev":{"headline":"Improper Privilege Management in X-Pack","id":"CVE-2017-8446"},"products":["Elastic X-Pack Security"],"published":"2017-09-28","related":[{"cvss_score":9.8,"headline":"Auth bypass in X-Pack Security","id":"CVE-2018-3822","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":8.8,"headline":"Privilege escalation in Elastic X-Pack Alerting","id":"CVE-2017-8448","kev_date_added":null,"published":"2017-09-28"},{"cvss_score":8.8,"headline":"Privilege escalation in X-Pack Security","id":"CVE-2017-8438","kev_date_added":null,"published":"2017-06-05"},{"cvss_score":7.5,"headline":"Missing authorization in Elastic X-Pack Security","id":"CVE-2017-8450","kev_date_added":null,"published":"2017-06-16"},{"cvss_score":6.5,"headline":"Information disclosure in Elasticsearch X-Pack Security","id":"CVE-2017-8442","kev_date_added":null,"published":"2017-07-07"},{"cvss_score":5.9,"headline":"Information disclosure in Elastic X-Pack Security","id":"CVE-2017-8449","kev_date_added":null,"published":"2017-06-16"}],"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":["Elastic"]},"summary":"Users with delete or index permissions can perform both actions, leading to privilege escalation and unauthorized data modification in Elastic clusters.","url":"https://insights.sbomify.com/CVE-2017-8447/"}