{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-3726 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-3726 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3726 is a high-severity command injection vulnerability in ohmyzsh/ohmyzsh, published on 30 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-3726 and fix it if it is affected.\n\nWhat it is: CVE-2021-3726 is a high-severity command injection vulnerability in ohmyzsh/ohmyzsh, published on 30 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-3726 in the wild and no public exploit code.\n\nAffected product: ohmyzsh/ohmyzsh. 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-2021-3726/ (Markdown: https://insights.sbomify.com/CVE-2021-3726/index.md)","id":"CVE-2021-3726","markdown":"https://insights.sbomify.com/CVE-2021-3726/index.md","name":"CVE-2021-3726","record":{"aliases":["GHSA-8jcw-2h4x-29pq"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Zsh configuration framework","requires_auth":"none","summary":"Attackers can execute arbitrary commands if custom user code unsafely uses the title function in Oh My Zsh.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"oh_my_zsh","vendor":"planetargon"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"# Vulnerability in `title` function **Description**: the `title` function defined in `lib/termsupport.zsh` uses `print` to set the terminal title to a user-supplied string. In Oh My Zsh, this function is always used securely, but custom user code could use the `title` function in a way that is unsafe. **Fixed in**: [a263cdac](https://github.com/ohmyzsh/ohmyzsh/commit/a263cdac). **Impacted areas**: - `title` function in `lib/termsupport.zsh`. - Custom user code using the `title` function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3726","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3727"},"packages":[],"prev":{"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3725"},"products":["ohmyzsh/ohmyzsh"],"published":"2021-11-30","related":[{"cvss_score":7.8,"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3934","kev_date_added":null,"published":"2021-11-12"},{"cvss_score":7.5,"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3725","kev_date_added":null,"published":"2021-11-30"},{"cvss_score":7.5,"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3727","kev_date_added":null,"published":"2021-11-30"},{"cvss_score":7.5,"headline":"OS Command Injection in ohmyzsh/ohmyzsh","id":"CVE-2021-3769","kev_date_added":null,"published":"2021-11-30"}],"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-03","vendors":["ohmyzsh"]},"summary":"Attackers can execute arbitrary commands if custom user code unsafely uses the title function in Oh My Zsh.","url":"https://insights.sbomify.com/CVE-2021-3726/"}