GHSA-vfm6-r2gc-pwww: Symfony/http foundation Symfony2 Security Issue When The Vulnerability
MODERATEGHSA-vfm6-r2gc-pwww is a MODERATE symfony2 security issue when the vulnerability (General Security Weakness) affecting Symfony/http foundation libraries in the Packagist ecosystem. The issue involves symfony2 security issue when the trust proxy mode is enabled. Remediation is available by upgrading affected packages to version 2.0.19, 2.1.4.
GHSA-vfm6-r2gc-pwww at a Glance
How to Fix GHSA-vfm6-r2gc-pwww
To remediate this vulnerability, upgrade all affected Symfony/http foundation dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade symfony/http-foundation to 2.0.19
Upgrade symfony/http-foundation to 2.1.4
Upgrade symfony/symfony to 2.0.19
Upgrade symfony/symfony to 2.1.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for symfony/http-foundation
How to Check if You Are Affected
To determine whether your application is affected by GHSA-vfm6-r2gc-pwww, inspect your project dependencies for Symfony/http foundation:
inspect dependencies for symfony/http-foundation
Analyze the terminal output to locate any version of Symfony/http foundation in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.19), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In Symfony/http foundation, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-vfm6-r2gc-pwww Affected Symfony/http foundation Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
symfony/http-foundation
|
Packagist |
≥ 2.0.0
< 2.0.19
|
2.0.19
|
|
symfony/http-foundation
|
Packagist |
≥ 2.1.0
< 2.1.4
|
2.1.4
|
|
symfony/symfony
|
Packagist |
≥ 2.0.0
< 2.0.19
|
2.0.19
|
|
symfony/symfony
|
Packagist |
≥ 2.1.0
< 2.1.4
|
2.1.4
|
References
Frequently Asked Questions
What is GHSA-vfm6-r2gc-pwww?
Which Symfony/http foundation versions are affected?
What version fixes GHSA-vfm6-r2gc-pwww?
Is symfony/http-foundation affected?
Is symfony/symfony affected?
What CWE is associated with GHSA-vfm6-r2gc-pwww?
How can I check Packagist dependencies for GHSA-vfm6-r2gc-pwww?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vfm6-r2gc-pwww",
"modified" : "2024-05-30T00:36:36Z",
"published" : "2024-05-30T00:34:48Z",
"aliases" : [ ],
"summary" : "Symfony2 security issue when the trust proxy mode is enabled",
"details" : "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.\n\nTo fix this security issue, the following changes have been made to all versions of Symfony2:\n\nA 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:\n```\n// before (probably in your front controller script)\nRequest::trustProxyData();\n\n// after\nRequest::setTrustedProxies(array('1.1.1.1'));\n// 1.1.1.1 being the IP address of a trusted reverse proxy\n```\nThe Request::trustProxyData() method has been deprecated (when used, it automatically trusts the latest proxy in the chain -- which is the current remote address):\n```\nRequest::trustProxyData();\n\n// is equivalent to\nRequest::setTrustedProxies(array($request->server->get('REMOTE_ADDR')));\n```\nWe 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:\n\n- [Patch](https://github.com/symfony/symfony/compare/fc89d6b...9ce892c.patch) for Symfony 2.0.19\n- [Patch](https://github.com/symfony/symfony/compare/922c201...e5536f0.patch) for Symfony 2.1.4",
"severity" : [ ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "symfony/http-foundation"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.0.19"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "symfony/http-foundation"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.1.0"
}, {
"fixed" : "2.1.4"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "symfony/symfony"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.0.19"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "symfony/symfony"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.1.0"
}, {
"fixed" : "2.1.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/symfony/http-foundation/commit/5cde5229fc71a19cef2a0a933a18e08e43252f34"
}, {
"type" : "WEB",
"url" : "https://github.com/symfony/http-foundation/commit/795ac45c188ee2a729db4513e9dfd30b16a0ed35"
}, {
"type" : "WEB",
"url" : "https://github.com/symfony/symfony/commit/9ce892cf4395e73b136e9b5cd1fae9e91995c93b"
}, {
"type" : "WEB",
"url" : "https://github.com/symfony/symfony/commit/e5536f0fe10421da7ebbe0071343e94d039dfb97"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/http-foundation/2012-11-29.yaml"
}, {
"type" : "WEB",
"url" : "https://symfony.com/blog/security-release-symfony-2-0-19-and-2-1-4"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2024-05-30T00:34:48Z",
"nvd_published_at" : null
}
}