{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7610 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-7610 is a critical code injection vulnerability in Elastic Kibana, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-7610 and fix it if it is affected.\n\nWhat it is: CVE-2019-7610 is a critical code injection vulnerability in Elastic Kibana, published on 25 Mar 2019. 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-2019-7610 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-2019-7610/ (Markdown: https://insights.sbomify.com/CVE-2019-7610/index.md)","id":"CVE-2019-7610","markdown":"https://insights.sbomify.com/CVE-2019-7610/index.md","name":"CVE-2019-7610","record":{"aliases":["GHSA-rrx3-4wcg-f297"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Kibana data visualization","requires_auth":"none","summary":"Attackers can execute arbitrary code on Kibana servers if the security audit logger is enabled, potentially compromising the host system.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Kibana versions before 6.6.1 contain an arbitrary code execution flaw in the security audit logger. If a Kibana instance has the setting xpack.security.audit.enabled set to true, an attacker could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system.","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":"Code injection in Kibana","id":"CVE-2019-7610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"elastic:kibana","products":["elastic:kibana"],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Improper Access Control in Elasticsearch","id":"CVE-2019-7611"},"packages":[],"prev":{"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609"},"products":["Kibana"],"published":"2019-03-25","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-04","vendors":["Elastic"]},"summary":"Attackers can execute arbitrary code on Kibana servers if the security audit logger is enabled, potentially compromising the host system.","url":"https://insights.sbomify.com/CVE-2019-7610/"}