# PSF-2019-15: Remove newline characters from uu encoding methods

> Attackers can corrupt file content during UU decoding by injecting newlines into filenames, affecting Python libraries using UU encoding.

- **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:** 30 Nov 2019

## What is PSF-2019-15?

PSF-2019-15 is a vulnerability, published on 30 Nov 2019. 

### Official description

Filenames passed to the UU encoding methods (uu.py and uu_codec.py) that
contain a newline character will overflow data into the UU content section.
This can potentially be used to inject replace or corrupt data content in a
file during the decode process.

The fix removes newline characters from filenames.

## Which versions are affected by PSF-2019-15?


## How do I fix PSF-2019-15?

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

## Is PSF-2019-15 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for PSF-2019-15 and fix it if it is affected.

What it is: PSF-2019-15 is a vulnerability, published on 30 Nov 2019. 
Exploitation: There is no known exploitation of PSF-2019-15 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-2019-15/ (Markdown: https://insights.sbomify.com/PSF-2019-15/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/PSF-2019-15

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