Summary
Symfony2 security issue when the trust proxy mode is enabled
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:
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
symfony/http-foundation to 2.0.19 or later; symfony/http-foundation to 2.1.4 or later; symfony/symfony to 2.0.19 or later; symfony/symfony to 2.1.4 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-VFM6-R2GC-PWWW? GHSA-VFM6-R2GC-PWWW is a medium-severity security vulnerability in symfony/http-foundation (composer), affecting versions >= 2.0.0, < 2.0.19. It is fixed in 2.0.19, 2.1.4.
- Which packages are affected by GHSA-VFM6-R2GC-PWWW?
symfony/http-foundation(composer) (versions >= 2.0.0, < 2.0.19)symfony/symfony(composer) (versions >= 2.0.0, < 2.0.19)
- Is there a fix for GHSA-VFM6-R2GC-PWWW? Yes. GHSA-VFM6-R2GC-PWWW is fixed in 2.0.19, 2.1.4. Upgrade to this version or later.
- Is GHSA-VFM6-R2GC-PWWW exploitable, and should I be worried? Whether GHSA-VFM6-R2GC-PWWW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-VFM6-R2GC-PWWW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-VFM6-R2GC-PWWW?
- Upgrade
symfony/http-foundationto 2.0.19 or later - Upgrade
symfony/http-foundationto 2.1.4 or later - Upgrade
symfony/symfonyto 2.0.19 or later - Upgrade
symfony/symfonyto 2.1.4 or later
- Upgrade