{"answers":{"affected":"2 open source packages ship an affected version, including tracexec.","exploited":"There is no known exploitation of GHSA-6fgx-x7m2-74qm in the wild and no public exploit code.","fix":"Upgrade tracexec to 0.14.0 or later.","what":"GHSA-6fgx-x7m2-74qm is a command injection vulnerability in tracexec, published on 13 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-6fgx-x7m2-74qm and fix it if it is affected.\n\nWhat it is: GHSA-6fgx-x7m2-74qm is a command injection vulnerability in tracexec, published on 13 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-6fgx-x7m2-74qm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tracexec (crates.io): affected all versions; fixed in 0.14.0\n- tracexec (crates.io): affected all versions; fixed in 0.14.0\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/GHSA-6fgx-x7m2-74qm/ (Markdown: https://insights.sbomify.com/GHSA-6fgx-x7m2-74qm/index.md)","id":"GHSA-6fgx-x7m2-74qm","markdown":"https://insights.sbomify.com/GHSA-6fgx-x7m2-74qm/index.md","name":"GHSA-6fgx-x7m2-74qm","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"tracexec CLI tool","requires_auth":"none","summary":"Attackers can inject arguments into the env command via environment variables, potentially leading to code execution if users copy and paste the reconstructed command line.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nFor tracexec's command line reconstruction feature, when a traced process executes another process with a environment variable where the key starts with a dash, tracexec incorrectly shows its commandline where such environment variables could cause argument injection for the `env` command.\nSuch an injection is completely at the UI level unless the user tries to copy the command line with the injection and paste it into a terminal to execute it.\n\nA minimal POC is executing `env -- -a=b bash --norc` in tracexec's TUI mode. The resulting command line of `env` executing bash would be `env -a bash -a=b  _=/usr/bin/env /usr/bin/bash --norc` in tracexec's TUI, which injects `-a=b` into `env`'s arguments.\n\nThis has very limited effect for security.  A local adversarial could leverage this to make tracexec show an inaccurate reconstructed commandline for their executed command. If the user of tracexec decides to copy and run the reconstructed commandline,\nthere could be injection for `env`'s `--block-signal`, `--default-signal`, `--ignore-signal`, `--split-string`, `--unset`, `--chdir`, `--argv0` arguments.\n\n### Patches\nThe fix is https://github.com/kxxt/tracexec/pull/118. Users are advised to upgrade to 0.14.0.\n\n### Workarounds\n\nDon't blindly paste and execute commands copied from tracexec that contains environment variable where the key starts with a dash.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"tracexec has `env` command argument injection via environment variables starting with dash in traced exec events","id":"GHSA-6fgx-x7m2-74qm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"tracexec","purl":null,"source":"GHSA-6fgx-x7m2-74qm"},{"ecosystem":"crates.io","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"tracexec","purl":"pkg:cargo/tracexec","source":"GHSA-6fgx-x7m2-74qm"}],"products":null,"published":"2025-10-13","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can inject arguments into the env command via environment variables, potentially leading to code execution if users copy and paste the reconstructed command line.","url":"https://insights.sbomify.com/GHSA-6fgx-x7m2-74qm/"}