Symfony2 getClientIp(): Faked Client IPs Can Get Past IP-Based Access Rules

Published as "Symfony2 improper IP based access control"

medium Symfony Symfony components · Last reviewed Nov 10, 2026

CVE: No CVE assigned
GHSA: GHSA-hx53-jchx-cr52
Packagist: PKSA-hx88-8gq9-rm71
Reported: May 30, 2024

Lets a client fake their IP address in Symfony 2.0 and 2.1 apps that call Request::trustProxyData() and use getClientIp() for access control.

Affected and fixed versions

In symfony/symfony. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
2.1.0 – 2.1.3	2.1.4
2.0.0 – 2.0.18	2.0.19

Upgrade

Run the line for the branch you are on.

composer require symfony/symfony:^2.1.4
composer require symfony/symfony:^2.0.19

What this means

A client could make your app see any IP address they chose. If your app used the client's IP to decide who gets in, such as an admin area limited to one network, an attacker could get past that check.

With trust proxy mode turned on through Request::trustProxyData(), Request::getClientIp() trusted forwarded IP headers without checking that they came from a proxy you trust. See Symfony's announcement and the patches for 2.0 and 2.1.

Who is affected

Apps on symfony/symfony 2.0 or 2.1 that call Request::trustProxyData() and use Request::getClientIp() for security decisions, such as IP-based access control. Apps that never turn on trust proxy mode aren't affected.

What to do

Update to 2.0.19 or 2.1.4. Then replace Request::trustProxyData() with Request::setTrustedProxies(), passing the IP addresses of your own reverse proxies. The old method is deprecated, and after the update it trusts only the address the request came from.

Symfony 2.0 and 2.1 stopped getting fixes long ago, so plan a move to a supported version.

Reported by Damien Tournoud of the Drupal security team.

Check your app with an agent

Paste this into a coding agent that can read your project, such as Claude Code, Codex or Amp. It checks your composer.lock against the versions above and tells you what to update, without changing anything.

Check whether the PHP project you have access to is affected by this security advisory, and tell me what to update. Do a read-only check: don't edit files, don't run composer update or composer require, and don't try to reproduce the flaw.

Advisory: Symfony2 getClientIp(): Faked Client IPs Can Get Past IP-Based Access Rules (GHSA-hx53-jchx-cr52)
Details: https://phpnews.net/security/symfony/ghsa-hx53-jchx-cr52

Affected versions, as Composer constraints:
- symfony/symfony: >=2.1.0,<2.1.4|>=2.0.0,<2.0.19

Fixed releases:
- 2.1.0 – 2.1.3: update to 2.1.4
- 2.0.0 – 2.0.18: update to 2.0.19

1. Find every composer.lock in the project outside vendor/ (a monorepo can have one per app) and read the installed version of each package above. Packages installed as dependencies of other packages count too.
2. Compare each installed version with its constraint: "|" separates alternative ranges, and "," means both bounds apply.
3. For each affected install, read "What this means" at https://phpnews.net/security/symfony/ghsa-hx53-jchx-cr52 and check whether the project meets the conditions it describes (a feature in use, a config value, a driver). Say which conditions you could check and which you couldn't.
4. Report a table: lock file | package | installed version | affected (yes, no or unknown) | conditions met (yes, no or unknown) | update to | evidence. For each affected package, give the command that would fix it, without running it: composer update <package> --with-dependencies when it is only installed as a dependency of another package, or composer require with the fixed version when composer.json requires it directly. If the installed version is on a branch with no fixed release listed, say it needs a move to a newer branch.

Sources

GitHub advisory GHSA-hx53-jchx-cr52 →

← All Symfony advisories