Headline
GHSA-p684-f7fh-jv2j: Symfony has unsafe methods in the Request class
All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, 2.5.X, and 2.6.X versions of the Symfony HttpFoundation component are affected by this security issue.
This issue has been fixed in Symfony 2.3.27, 2.5.11, and 2.6.6. Note that no fixes are provided for Symfony 2.0, 2.1, 2.2, and 2.4 as they are not maintained anymore.
Description
The Symfony\Component\HttpFoundation\Request class provides a mechanism that ensures it does not trust HTTP header values coming from a “non-trusted” client. Unfortunately, it assumes that the remote address is always a trusted client if at least one trusted proxy is involved in the request; this allows a man-in-the-middle attack between the latest trusted proxy and the web server.
The following methods are impacted: getPort(), isSecure(), and getHost(), and getClientIps().
Resolution
All impacted methods now check that the remote address is trusted, which fixes the issue.
The patch for this issue is available here.
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2015-2309
Symfony has unsafe methods in the Request class
Moderate severity GitHub Reviewed Published May 30, 2024 to the GitHub Advisory Database • Updated May 30, 2024
Package
composer symfony/http-foundation (Composer)
Affected versions
>= 2.0.0, < 2.3.27
>= 2.4.0, < 2.5.11
>= 2.6.0, < 2.6.6
Patched versions
2.3.27
2.5.11
2.6.6
>= 2.0.0, < 2.3.27
>= 2.4.0, < 2.5.11
>= 2.6.0, < 2.6.6
All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, 2.5.X, and 2.6.X versions of the Symfony HttpFoundation component are affected by this security issue.
This issue has been fixed in Symfony 2.3.27, 2.5.11, and 2.6.6. Note that no fixes are provided for Symfony 2.0, 2.1, 2.2, and 2.4 as they are not maintained anymore.
Description
The Symfony\Component\HttpFoundation\Request class provides a mechanism that ensures it does not trust HTTP header values coming from a “non-trusted” client. Unfortunately, it assumes that the remote address is always a trusted client if at least one trusted proxy is involved in the request; this allows a man-in-the-middle attack between the latest trusted proxy and the web server.
The following methods are impacted: getPort(), isSecure(), and getHost(), and getClientIps().
Resolution
All impacted methods now check that the remote address is trusted, which fixes the issue.
The patch for this issue is available here.
References
- symfony/symfony#14166
- symfony/symfony@6c73f0c
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/http-foundation/CVE-2015-2309.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2015-2309.yaml
- https://symfony.com/cve-2015-2309
Published to the GitHub Advisory Database
May 30, 2024
Last updated
May 30, 2024