# GHSA-4qpj-gxxg-jqg4: Swiftmailer Sendmail transport arbitrary shell execution

> Attackers can execute arbitrary shell commands via the From header in Swiftmailer's sendmail transport when Return-Path is unconfigured.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2024

## What is GHSA-4qpj-gxxg-jqg4?

GHSA-4qpj-gxxg-jqg4 is a command injection vulnerability in swiftmailer/swiftmailer, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prior to 5.2.1, the sendmail transport (`Swift_Transport_SendmailTransport`) was vulnerable to an arbitrary shell execution if the "From" header came from a non-trusted source and no "Return-Path" is configured. This has been fixed in 5.2.1. If you are using sendmail as a transport, you are encouraged to upgrade as soon as possible.

## Which versions are affected by GHSA-4qpj-gxxg-jqg4?

2 open source packages ship an affected version, including swiftmailer/swiftmailer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `swiftmailer/swiftmailer` | Packagist | From 4.0.0 | 5.2.1 |
| `swiftmailer/swiftmailer` | Packagist | From 4.0.0 | 5.2.1 |

## How do I fix GHSA-4qpj-gxxg-jqg4?

Upgrade swiftmailer/swiftmailer to 5.2.1 or later.

## Is GHSA-4qpj-gxxg-jqg4 being exploited?

There is no known exploitation of GHSA-4qpj-gxxg-jqg4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4qpj-gxxg-jqg4 and fix it if it is affected.

What it is: GHSA-4qpj-gxxg-jqg4 is a command injection vulnerability in swiftmailer/swiftmailer, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4qpj-gxxg-jqg4 in the wild and no public exploit code.

Affected packages and fixed versions:
- swiftmailer/swiftmailer (Packagist): affected from 4.0.0; fixed in 5.2.1
- swiftmailer/swiftmailer (Packagist): affected from 4.0.0; fixed in 5.2.1

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/GHSA-4qpj-gxxg-jqg4/ (Markdown: https://insights.sbomify.com/GHSA-4qpj-gxxg-jqg4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4qpj-gxxg-jqg4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4qpj-gxxg-jqg4/
Summaries are generated and may contain mistakes; the official description above is the record.