# PSF-2017-8: Environment variables injection in subprocess on Windows

> Attackers can inject environment variables or arguments into subprocess calls on Windows, potentially leading to arbitrary code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2017

## What is PSF-2017-8?

PSF-2017-8 is a command injection vulnerability, published on 22 Jun 2017. 

### Official description

On Windows, prevent passing invalid environment variables and command
arguments to subprocess.Popen.

It is possible to inject an environment variable in subprocess on Windows
if a user data is passed to a subprocess via environment variable.

Check for invalid environment (variable names containing '=') and command
arguments (containing '\0').

## Which versions are affected by PSF-2017-8?


## How do I fix PSF-2017-8?

No fix has been published for PSF-2017-8 yet. Limit exposure of the affected software until one is available.

## Is PSF-2017-8 being exploited?

There is no known exploitation of PSF-2017-8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for PSF-2017-8 and fix it if it is affected.

What it is: PSF-2017-8 is a command injection vulnerability, published on 22 Jun 2017. 
Exploitation: There is no known exploitation of PSF-2017-8 in the wild and no public exploit code.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/PSF-2017-8/ (Markdown: https://insights.sbomify.com/PSF-2017-8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/PSF-2017-8

---
From sbomify Insights: https://insights.sbomify.com/PSF-2017-8/
Summaries are generated and may contain mistakes; the official description above is the record.