{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-1000219 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2016-1000219 is a high-severity vulnerability in Elastic Kibana, 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-2016-1000219 and fix it if it is affected.\n\nWhat it is: CVE-2016-1000219 is a high-severity vulnerability in Elastic Kibana, 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-2016-1000219 in the wild and no public exploit code.\n\nAffected product: Elastic Kibana. 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-2016-1000219/ (Markdown: https://insights.sbomify.com/CVE-2016-1000219/index.md)","id":"CVE-2016-1000219","markdown":"https://insights.sbomify.com/CVE-2016-1000219/index.md","name":"CVE-2016-1000219","record":{"aliases":["GHSA-q36m-wm9g-699v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Kibana logging","requires_auth":"none","summary":"Attackers can hijack user sessions by reading sensitive cookies and authorization headers from log files when custom logging outputs are configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kibana","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:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"Kibana before 4.5.4 and 4.1.11 when a custom output is configured for logging in, cookies and authorization headers could be written to the log files. This information could be used to hijack sessions of other users when using Kibana behind some form of authentication such as Shield.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2016-1000219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:kibana","products":["elastic:kibana"],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2016-1000220"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2016-1000218"},"products":["n/a"],"published":"2017-06-16","related":[{"cvss_score":9.8,"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609","kev_date_added":"2022-01-10","published":"2019-03-25"},{"cvss_score":9.9,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25015","kev_date_added":null,"published":"2025-03-05"},{"cvss_score":9.9,"headline":"Deserialization in Kibana","id":"CVE-2024-37288","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.9,"headline":"Code injection in Kibana","id":"CVE-2023-31415","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.8,"headline":"Information disclosure in Kibana","id":"CVE-2018-17245","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Code injection in Kibana","id":"CVE-2018-17246","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.1,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25014","kev_date_added":null,"published":"2025-05-06"}],"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":"Attackers can hijack user sessions by reading sensitive cookies and authorization headers from log files when custom logging outputs are configured.","url":"https://insights.sbomify.com/CVE-2016-1000219/"}