# GHSA-8jp9-mpv9-98rj: amphp/http-client Header leakage on cross-domain redirects

> An attacker can leak sensitive request headers to a different host during cross-domain redirects in the amphp/http-client library.

- **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:** 15 May 2024

## What is GHSA-8jp9-mpv9-98rj?

GHSA-8jp9-mpv9-98rj is a vulnerability in amphp/http-client, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

amphp/http-client has a security weakness that might leak sensitive request headers from the initial request to the redirected host on cross-domain redirects, which were not removed correctly. `Message::setHeaders` does not replace the entire set of headers, but only operates on the headers matching the given array keys.

## Which versions are affected by GHSA-8jp9-mpv9-98rj?

2 open source packages ship an affected version, including amphp/http-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `amphp/http-client` | Packagist | From 4.0.0 | 4.4.0 |
| `amphp/http-client` | Packagist | From 4.0.0 | 4.4.0 |

## How do I fix GHSA-8jp9-mpv9-98rj?

Upgrade amphp/http-client to 4.4.0 or later.

## Is GHSA-8jp9-mpv9-98rj being exploited?

There is no known exploitation of GHSA-8jp9-mpv9-98rj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8jp9-mpv9-98rj and fix it if it is affected.

What it is: GHSA-8jp9-mpv9-98rj is a vulnerability in amphp/http-client, published on 15 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-8jp9-mpv9-98rj in the wild and no public exploit code.

Affected packages and fixed versions:
- amphp/http-client (Packagist): affected from 4.0.0; fixed in 4.4.0
- amphp/http-client (Packagist): affected from 4.0.0; fixed in 4.4.0

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-8jp9-mpv9-98rj/ (Markdown: https://insights.sbomify.com/GHSA-8jp9-mpv9-98rj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8jp9-mpv9-98rj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8jp9-mpv9-98rj/
Summaries are generated and may contain mistakes; the official description above is the record.