How severe is GHSA-vfm6-r2gc-pwww?

No CVSS score has been assigned to GHSA-vfm6-r2gc-pwww yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vfm6-r2gc-pwww?

GHSA-vfm6-r2gc-pwww affects the following packages: symfony/http-foundation (Packagist), symfony/http-foundation (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist). Ecosystems affected: Packagist.

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

Update symfony/http-foundation to 2.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfm6-r2gc-pwww is resolved across your whole dependency graph.

How do I detect GHSA-vfm6-r2gc-pwww in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/http-foundation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vfm6-r2gc-pwww if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-vfm6-r2gc-pwww actively exploited in the wild?

No public exploit code has been indexed for GHSA-vfm6-r2gc-pwww yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vfm6-r2gc-pwww published, and has it been updated?

GHSA-vfm6-r2gc-pwww was published on May 30, 2024 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Symfony2 security issue when the trust proxy mode is enabledGHSA-vfm6-r2gc-pwww

Fix: symfony/http-foundation@5cde522

GHSA-vfm6-r2gc-pwww is a security vulnerability in symfony/http-foundation. A fix is available for symfony/http-foundation — see the affected versions and patch details below.

Published

May 30, 2024

Updated

Dec 4, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/symfony🐘symfony/symfony

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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 for Symfony 2.0.19
Patch for Symfony 2.1.4

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/http-foundation`	≥ 2.0.0&&< 2.0.19	2.0.19`composer require symfony/http-foundation:^2.0.19`
🐘Packagist	`symfony/http-foundation`	≥ 2.1.0&&< 2.1.4	2.1.4`composer require symfony/http-foundation:^2.1.4`
🐘Packagist	`symfony/symfony`	≥ 2.0.0&&< 2.0.19	2.0.19`composer require symfony/symfony:^2.0.19`
🐘Packagist	`symfony/symfony`	≥ 2.1.0&&< 2.1.4	2.1.4`composer require symfony/symfony:^2.1.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/http-foundation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/http-foundation to 2.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfm6-r2gc-pwww is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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(arra

O3 Security · Impact-Aware SCA

Is GHSA-vfm6-r2gc-pwww in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works