RCE in Symfony
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-kernel Packagist |
|
|
| symfony/symfony Packagist |
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-kernel Packagist |
|
|
| symfony/symfony Packagist |
|
|
In Symfony before versions 4.4.13 and 5.1.5, the CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible. This has been fixed in versions 4.4.13 and 5.1.5.
From the CVE record · GitHub_M
Symfony’s CachingHttpClient relies on HttpCache, which uses internal headers to restore cached responses. A remote attacker who can control a response to a request made by CachingHttpClient can execute code.
Check applications using Packagist symfony/http-kernel or symfony/symfony versions >=4.3.0 <4.4.13 or >=5.0.0 <5.1.5.