RCE in Symfony
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.13, 5.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- symfony symfony
From 4.4.0 · fixed in 4.4.13; From 5.0.0 · fixed in 5.1.5
- symfony/http-kernelPackagist
From 4.3.0 · fixed in 4.4.13
- symfony/http-kernelPackagist
From 5.0.0 · fixed in 5.1.5
- symfony/symfonyPackagist
From 4.3.0 · fixed in 4.4.13
- symfony/symfonyPackagist
From 5.0.0 · fixed in 5.1.5