Symfony HttpClient: NoPrivateNetworkHttpClient Leaks Internal Hosts and Ports

Published as "CVE-2024-50342: Internal address and port enumeration allowed by NoPrivateNetworkHttpClient"

low Symfony Symfony components · Last reviewed Nov 9, 2026

CVE: CVE-2024-50342
GHSA: GHSA-9c3x-r3wp-mgxm
Packagist: PKSA-4k7v-pfvw-nqvp
Reported: Nov 13, 2024

Can let an attacker map internal IP addresses and ports through apps that fetch user-supplied URLs with NoPrivateNetworkHttpClient.

Affected and fixed versions

In 2 packages: symfony/http-client and symfony/symfony. Find the row for the version you run, and update to the release next to it.

If you run	Update to	Support
6.4.0 – 6.4.14	6.4.15	Supported
5.4.0 – 5.4.46	5.4.47	Supported

Show 12 older branches, no longer supported

7.0.0 – 7.0.x	7.1.8
7.1.0 – 7.1.7	7.1.8
6.0.0 – 6.0.x	6.4.15
6.1.0 – 6.1.x	6.4.15
6.2.0 – 6.2.x	6.4.15
6.3.0 – 6.3.x	6.4.15
4.3.0 – 4.3.x	5.4.47
4.4.0 – 4.x	5.4.47
5.0.0 – 5.0.x	5.4.47
5.1.0 – 5.1.x	5.4.47
5.2.0 – 5.2.x	5.4.47
5.3.0 – 5.3.x	5.4.47

Upgrade

Run the line for the branch you are on. 1 other package listed above is affected too; update it the same way.

composer require symfony/http-client:^6.4.15
composer require symfony/http-client:^5.4.47

What this means

NoPrivateNetworkHttpClient is meant to stop your app from sending requests into private networks. Apps use it against server-side request forgery (SSRF), where an attacker makes your server request places it shouldn't. Before this fix, it still leaked some information while resolving a host name, so an attacker could work out which internal IP addresses and ports exist.

Who is affected

Apps that wrap their HTTP client in Symfony\Component\HttpClient\NoPrivateNetworkHttpClient to fetch URLs that users can choose. Affected releases of symfony/http-client (and symfony/symfony) are 4.3.0 and later below 5.4.47, 6.x below 6.4.15, and 7.x below 7.1.8. Apps that don't use this class are not affected. Symfony rates it low: the leak is limited to address and port details.

What to do

Update to 5.4.47, 6.4.15 or 7.1.8. Symfony's advisory notes that 5.4.46, 6.4.14 and 7.1.7 shipped a first fix that was incomplete, so those releases are still affected. The fixes are here and here.

Reported by Linus Karlsson and Chris Smith.

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: Symfony HttpClient: NoPrivateNetworkHttpClient Leaks Internal Hosts and Ports (CVE-2024-50342, GHSA-9c3x-r3wp-mgxm)
Details: https://phpnews.net/security/symfony/ghsa-9c3x-r3wp-mgxm

Affected versions, as Composer constraints:
- symfony/http-client, symfony/symfony: >=4.3.0,<4.4.0|>=4.4.0,<5.0.0|>=5.0.0,<5.1.0|>=5.1.0,<5.2.0|>=5.2.0,<5.3.0|>=5.3.0,<5.4.0|>=5.4.0,<5.4.47|>=6.0.0,<6.1.0|>=6.1.0,<6.2.0|>=6.2.0,<6.3.0|>=6.3.0,<6.4.0|>=6.4.0,<6.4.15|>=7.0.0,<7.1.0|>=7.1.0,<7.1.8

Fixed releases on branches that still get security fixes:
- 6.4.0 – 6.4.14: update to 6.4.15
- 5.4.0 – 5.4.46: update to 5.4.47

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-9c3x-r3wp-mgxm and check whether the project meets the conditions it describes (a feature in use, a config value, a driver) (if that page won't load, use https://github.com/advisories/GHSA-9c3x-r3wp-mgxm). 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

← All Symfony advisories