{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5029 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5029 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5029 is a critical command injection vulnerability in Exhibitor, published on 13 Nov 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-5029 and fix it if it is affected.\n\nWhat it is: CVE-2019-5029 is a critical command injection vulnerability in Exhibitor, published on 13 Nov 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-5029 in the wild and no public exploit code.\n\nAffected product: Exhibitor. 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-5029/ (Markdown: https://insights.sbomify.com/CVE-2019-5029/index.md)","id":"CVE-2019-5029","markdown":"https://insights.sbomify.com/CVE-2019-5029/index.md","name":"CVE-2019-5029","record":{"aliases":["GHSA-vq4h-pfrp-qjjj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ZooKeeper management tool","requires_auth":"none","summary":"Attackers can execute arbitrary shell commands via the Exhibitor Web UI Config editor, compromising the server running ZooKeeper.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"exhibitor","vendor":"exhibitor_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An exploitable command injection vulnerability exists in the Config editor of the Exhibitor Web UI versions 1.0.9 to 1.7.1. Arbitrary shell commands surrounded by backticks or $() can be inserted into the editor and will be executed by the Exhibitor process when it launches ZooKeeper. An attacker can execute any command as the user running the Exhibitor process.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-07-07","github_poc":2,"max_poc_stars":5,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-12-14T01:05:45Z","kind":"github_poc","ref":"https://github.com/thehunt1s0n/Exihibitor-RCE","stars":5,"title":"Exihibitor Web Ui 1.7.1 RCE, CVE-2019-5029"},{"date":"2020-07-07","kind":"exploitdb","ref":"48654","stars":null,"title":"Exhibitor Web UI 1.7.1 - Remote Code Execution"},{"date":"2025-01-16T08:34:58Z","kind":"github_poc","ref":"https://github.com/yZee00/CVE-2019-5029","stars":0,"title":"This is a Python script PoC for CVE-2019-5029"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Command injection in Exhibitor","id":"CVE-2019-5029","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Antenna House","id":"CVE-2019-5030"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-5028"},"products":["Exhibitor"],"published":"2019-11-13","related":[],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary shell commands via the Exhibitor Web UI Config editor, compromising the server running ZooKeeper.","url":"https://insights.sbomify.com/CVE-2019-5029/"}