{"answers":{"affected":"","exploited":"There is no known exploitation of PSF-2017-8 in the wild and no public exploit code.","fix":"No fix has been published for PSF-2017-8 yet. Limit exposure of the affected software until one is available.","what":"PSF-2017-8 is a command injection vulnerability, published on 22 Jun 2017."},"fix_prompt":"Check this codebase for PSF-2017-8 and fix it if it is affected.\n\nWhat it is: PSF-2017-8 is a command injection vulnerability, published on 22 Jun 2017. \nExploitation: There is no known exploitation of PSF-2017-8 in the wild and no public exploit code.\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/PSF-2017-8/ (Markdown: https://insights.sbomify.com/PSF-2017-8/index.md)","id":"PSF-2017-8","markdown":"https://insights.sbomify.com/PSF-2017-8/index.md","name":"PSF-2017-8","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Python subprocess library","requires_auth":"none","summary":"Attackers can inject environment variables or arguments into subprocess calls on Windows, potentially leading to arbitrary code execution.","user_interaction":"not_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":"On Windows, prevent passing invalid environment variables and command\narguments to subprocess.Popen.\n\nIt is possible to inject an environment variable in subprocess on Windows\nif a user data is passed to a subprocess via environment variable.\n\nCheck for invalid environment (variable names containing '=') and command\narguments (containing '\\0').","ecosystems":[],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Environment variables injection in subprocess on Windows","id":"PSF-2017-8","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2017"},"n_packages":0,"n_references":null,"packages":[],"products":null,"published":"2017-06-22","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"Python Software Foundation","prefix":"PSF"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can inject environment variables or arguments into subprocess calls on Windows, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/PSF-2017-8/"}