{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1880 exists.","fix":"No fix has been published for CVE-2024-1880 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1880 is a high-severity command injection vulnerability in significant-gravitas/autogpt, published on 6 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-1880 and fix it if it is affected.\n\nWhat it is: CVE-2024-1880 is a high-severity command injection vulnerability in significant-gravitas/autogpt, published on 6 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1880 exists.\n\nAffected product: significant-gravitas/autogpt. 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-1880/ (Markdown: https://insights.sbomify.com/CVE-2024-1880/index.md)","id":"CVE-2024-1880","markdown":"https://insights.sbomify.com/CVE-2024-1880/index.md","name":"CVE-2024-1880","record":{"aliases":["GHSA-rf3r-wjj9-3842"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AutoGPT AI agent","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code on macOS systems running AutoGPT with text-to-speech enabled via OS command injection in the speech module.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"autogpt_classic","vendor":"agpt"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/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 OS command injection vulnerability exists in the MacOS Text-To-Speech class MacOSTTS of the significant-gravitas/autogpt project, affecting versions up to v0.5.0. The vulnerability arises from the improper neutralization of special elements used in an OS command within the `_speech` method of the MacOSTTS class. Specifically, the use of `os.system` to execute the `say` command with user-supplied text allows for arbitrary code execution if an attacker can inject shell commands. This issue is triggered when the AutoGPT instance is run with the `--speak` option enabled and configured with `TEXT_TO_SPEECH_PROVIDER=macos`, reflecting back a shell injection snippet. The impact of this vulnerability is the potential execution of arbitrary code on the instance running AutoGPT. The issue was addressed in version 5.1.0.","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":"OS Command Injection in MacOS Text-To-Speech Class in significant-gravitas/autogpt","id":"CVE-2024-1880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Neutralization of Special Elements used in an OS Command in significant-gravitas/autogpt","id":"CVE-2024-1881"},"packages":[],"prev":{"headline":"CSRF to RCE in significant-gravitas/autogpt","id":"CVE-2024-1879"},"products":["significant-gravitas/autogpt"],"published":"2024-06-06","related":[{"cvss_score":9.8,"headline":"Shell Command Denylist Bypass in significant-gravitas/autogpt","id":"CVE-2024-6091","kev_date_added":null,"published":"2024-09-11"},{"cvss_score":8.8,"headline":"Command Injection in significant-gravitas/autogpt","id":"CVE-2024-8156","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.8,"headline":"CSRF to RCE in significant-gravitas/autogpt","id":"CVE-2024-1879","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.8,"headline":"Improper Neutralization of Special Elements used in an OS Command in significant-gravitas/autogpt","id":"CVE-2024-1881","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.1,"headline":"Docker escape in Auto-GPT when running from docker-compose.yml included in git repo","id":"CVE-2023-37273","kev_date_added":null,"published":"2023-07-13"},{"cvss_score":7.6,"headline":"Python code execution sandbox escape in non-docker version in Auto-GPT","id":"CVE-2023-37274","kev_date_added":null,"published":"2023-07-13"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["significant-gravitas"]},"summary":"Attackers can execute arbitrary code on macOS systems running AutoGPT with text-to-speech enabled via OS command injection in the speech module.","url":"https://insights.sbomify.com/CVE-2024-1880/"}