CVE-2020-5274GHSA-M884-279H-32V2BIT-SYMFONY-2020-5274
Exceptions displayed in non-debug configurations 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.5, 5.0.5, 4.4.4, 5.0.4
- 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 5.0.5 and 4.4.5, some properties of the Exception were not properly escaped when the `ErrorHandler` rendered it stacktrace. In addition, the stacktrace were displayed even in a non-debug configuration. The ErrorHandler now escape alls properties of the exception, and the stacktrace is only display in debug configuration. This issue is patched in symfony/http-foundation versions 4.4.5 and 5.0.5
Timeline
- CVE published
- Record last updated
Affected versions
- symfony symfony
From 4.0.0 · fixed in 4.4.5; From 5.0.0 · fixed in 5.0.5
- symfony/error-handlerPackagist
From 4.4.0 · fixed in 4.4.4
- symfony/error-handlerPackagist
From 5.0.0 · fixed in 5.0.4
- symfony/symfonyPackagist
From 4.4.0 · fixed in 4.4.4
- symfony/symfonyPackagist
From 5.0.0 · fixed in 5.0.4