# GHSA-vfm6-r2gc-pwww: Symfony2 security issue when the trust proxy mode is enabled

> Attackers can bypass IP-based access controls in Symfony applications using trust proxy mode by spoofing client IPs.

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

## What is GHSA-vfm6-r2gc-pwww?

GHSA-vfm6-r2gc-pwww is a vulnerability in symfony/http-foundation, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An application is vulnerable if it uses the client IP address as returned by the Request::getClientIp() method for sensitive decisions like IP based access control.

To fix this security issue, the following changes have been made to all versions of Symfony2:

A new Request::setTrustedProxies() method has been introduced and should be used intead of Request::trustProxyData() to enable the trust proxy mode. It takes an array of trusted proxy IP addresses as its argument:
```
// before (probably in your front controller script)
Request::trustProxyData();

// after
Request::setTrustedProxies(array('1.1.1.1'));
// 1.1.1.1 being the IP address of a trusted reverse proxy
```
The Request::trustProxyData() method has been deprecated (when used, it automatically trusts the latest proxy in the chain -- which is the current remote address):
```
Request::trustProxyData();

// is equivalent to
Request::setTrustedProxies(array($request->server->get('REMOTE_ADDR')));
```
We encourage all Symfony2 users to upgrade as soon as possible. It you don't want to upgrade to the latest version yet, you can also apply the following patches:

- [Patch](https://github.com/symfony/symfony/compare/fc89d6b...9ce892c.patch) for Symfony 2.0.19
- [Patch](https://github.com/symfony/symfony/compare/922c201...e5536f0.patch) for Symfony 2.1.4

## Which versions are affected by GHSA-vfm6-r2gc-pwww?

8 open source packages ship an affected version, including symfony/http-foundation and symfony/symfony.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/http-foundation` | Packagist | From 2.0.0 | 2.0.19 |
| `symfony/http-foundation` | Packagist | From 2.0.0 | 2.0.19 |
| `symfony/http-foundation` | Packagist | From 2.1.0 | 2.1.4 |
| `symfony/http-foundation` | Packagist | From 2.1.0 | 2.1.4 |
| `symfony/symfony` | Packagist | From 2.0.0 | 2.0.19 |
| `symfony/symfony` | Packagist | From 2.0.0 | 2.0.19 |
| `symfony/symfony` | Packagist | From 2.1.0 | 2.1.4 |
| `symfony/symfony` | Packagist | From 2.1.0 | 2.1.4 |

## How do I fix GHSA-vfm6-r2gc-pwww?

Upgrade symfony/http-foundation to a fixed version for your release line: 2.0.19 or 2.1.4.

## Is GHSA-vfm6-r2gc-pwww being exploited?

There is no known exploitation of GHSA-vfm6-r2gc-pwww in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vfm6-r2gc-pwww and fix it if it is affected.

What it is: GHSA-vfm6-r2gc-pwww is a vulnerability in symfony/http-foundation, published on 30 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-vfm6-r2gc-pwww in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/http-foundation (Packagist): affected from 2.0.0; fixed in 2.0.19
- symfony/http-foundation (Packagist): affected from 2.0.0; fixed in 2.0.19
- symfony/http-foundation (Packagist): affected from 2.1.0; fixed in 2.1.4
- symfony/http-foundation (Packagist): affected from 2.1.0; fixed in 2.1.4
- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.19
- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.19
- symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.4
- symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.4

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-vfm6-r2gc-pwww/ (Markdown: https://insights.sbomify.com/GHSA-vfm6-r2gc-pwww/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vfm6-r2gc-pwww

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vfm6-r2gc-pwww/
Summaries are generated and may contain mistakes; the official description above is the record.