GHSA-vfm6-r2gc-pwww json
Symfony2 security issue when the trust proxy mode is enabled
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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](https://github.com/symfony/symfony/compare/fc89d6b...9ce892c.patch) for Symfony 2.0.19 - [Patch](https://github.com/symfony/symfony/compare/922c201...e5536f0.patch) for Symfony 2.1.4
Patch / fix
- packagist symfony/http-foundation 2.0.19, 2.1.4
- packagist symfony/symfony 2.0.19, 2.1.4
Is GHSA-vfm6-r2gc-pwww in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | symfony/http-foundation | >=2.0.0, <2.0.19 >=2.1.0, <2.1.4 |
2.0.19 2.1.4 |
| packagist | symfony/symfony | >=2.0.0, <2.0.19 >=2.1.0, <2.1.4 |
2.0.19 2.1.4 |
References
-
github.com
/symfony/http-foundation/commit/5cde5229fc71a19cef2a0a933a18e08e43252f34
web
-
github.com
/symfony/http-foundation/commit/795ac45c188ee2a729db4513e9dfd30b16a0ed35
web
-
github.com
/symfony/symfony/commit/9ce892cf4395e73b136e9b5cd1fae9e91995c93b
web
-
github.com
/symfony/symfony/commit/e5536f0fe10421da7ebbe0071343e94d039dfb97
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/symfony/http-foundation/2012-11-29.yaml
web
-
symfony.com
/blog/security-release-symfony-2-0-19-and-2-1-4
web
Sources
- GitHub Advisory GHSA-vfm6-r2gc-pwww
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.