{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2359 exists.","fix":"No fix has been published for CVE-2024-2359 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2359 is a critical command injection vulnerability in parisneo/lollms-webui, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-2359 and fix it if it is affected.\n\nWhat it is: CVE-2024-2359 is a critical command injection vulnerability in parisneo/lollms-webui, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2359 exists.\n\nAffected product: parisneo/lollms-webui. 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-2024-2359/ (Markdown: https://insights.sbomify.com/CVE-2024-2359/index.md)","id":"CVE-2024-2359","markdown":"https://insights.sbomify.com/CVE-2024-2359/index.md","name":"CVE-2024-2359","record":{"aliases":["GHSA-jhmr-hfhr-vhq6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lollms Web UI","requires_auth":"none","summary":"Attackers can bypass access restrictions via an unsecured settings endpoint to enable remote code execution on the Lollms Web UI server.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms_web_ui","vendor":"lollms"}],"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":"A vulnerability in the parisneo/lollms-webui version 9.3 allows attackers to bypass intended access restrictions and execute arbitrary code. The issue arises from the application's handling of the `/execute_code` endpoint, which is intended to be blocked from external access by default. However, attackers can exploit the `/update_setting` endpoint, which lacks proper access control, to modify the `host` configuration at runtime. By changing the `host` setting to an attacker-controlled value, the restriction on the `/execute_code` endpoint can be bypassed, leading to remote code execution. This vulnerability is due to improper neutralization of special elements used in an OS command (`Improper Neutralization of Special Elements used in an OS Command`).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Improper Neutralization of Special Elements used in an OS Command in parisneo/lollms-webui","id":"CVE-2024-2359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2360"},"packages":[],"prev":{"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2358"},"products":["parisneo/lollms-webui"],"published":"2024-06-06","related":[{"cvss_score":9.8,"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2360","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.8,"headline":"Remote Code Execution due to LFI in '/install_extension' in parisneo/lollms-webui","id":"CVE-2024-4320","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.8,"headline":"Path Traversal leading to Remote Code Execution in parisneo/lollms-webui","id":"CVE-2024-2358","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":9.8,"headline":"Remote Code Execution via `/apply_settings` and `/execute_code` in parisneo/lollms-webui","id":"CVE-2024-4326","kev_date_added":null,"published":"2024-05-16"},{"cvss_score":9.8,"headline":"Path Traversal Vulnerability in parisneo/lollms-webui","id":"CVE-2024-1511","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.8,"headline":"OS Command Injection in parisneo/lollms-webui","id":"CVE-2024-1520","kev_date_added":null,"published":"2024-04-10"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["parisneo"]},"summary":"Attackers can bypass access restrictions via an unsecured settings endpoint to enable remote code execution on the Lollms Web UI server.","url":"https://insights.sbomify.com/CVE-2024-2359/"}