# PSF-2019-16: Email header injection in Address objects

> Attackers can inject email headers via CR/LF characters in Address objects, potentially altering email content or routing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2019

## What is PSF-2019-16?

PSF-2019-16 is a vulnerability, published on 17 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It is possible to inject email headers using CR or LF character.

The fix disallows CR and LF characters in ``email.headerregistry.Address``
arguments to guard against header injection attacks.

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


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

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

## Is PSF-2019-16 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: PSF-2019-16 is a vulnerability, published on 17 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of PSF-2019-16 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-16/ (Markdown: https://insights.sbomify.com/PSF-2019-16/index.md)
```

## Sources

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

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