{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8450 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8450 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8450 is a high-severity missing authorization vulnerability in Elastic X-Pack Security, published on 16 Jun 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-8450 and fix it if it is affected.\n\nWhat it is: CVE-2017-8450 is a high-severity missing authorization vulnerability in Elastic X-Pack Security, published on 16 Jun 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-8450 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-8450/ (Markdown: https://insights.sbomify.com/CVE-2017-8450/index.md)","id":"CVE-2017-8450","markdown":"https://insights.sbomify.com/CVE-2017-8450/index.md","name":"CVE-2017-8450","record":{"aliases":["GHSA-h63x-5x88-qfh6"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic X-Pack Security","requires_auth":"none","summary":"Users without proper access rights could read restricted documents and fields via multi-search or multi-get requests in Elastic X-Pack.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"x-pack","vendor":"elastic"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"},{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"X-Pack 5.1.1 did not properly apply document and field level security to multi-search and multi-get requests so users without access to a document and/or field may have been able to access this information.","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 Elastic X-Pack Security","id":"CVE-2017-8450","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":"Open redirect in Elastic X-Pack Security","id":"CVE-2017-8451"},"packages":[],"prev":{"headline":"Information disclosure in Elastic X-Pack Security","id":"CVE-2017-8449"},"products":["Elastic X-Pack Security"],"published":"2017-06-16","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":6.5,"headline":"Privilege escalation in Elastic X-Pack Security","id":"CVE-2017-8447","kev_date_added":null,"published":"2017-09-28"},{"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 without proper access rights could read restricted documents and fields via multi-search or multi-get requests in Elastic X-Pack.","url":"https://insights.sbomify.com/CVE-2017-8450/"}