CVE-2020-5274:
Exceptions displayed in non-debug configurations in Symfony
4.6
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.50041%
CWE
Published
3/30/2020
Updated
2/6/2024
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
symfony/error-handler | composer | >= 4.4.0, < 4.4.4 | 4.4.4 |
symfony/error-handler | composer | >= 5.0.0, < 5.0.4 | 5.0.4 |
symfony/symfony | composer | >= 4.4.0, < 4.4.4 | 4.4.4 |
symfony/symfony | composer | >= 5.0.0, < 5.0.4 | 5.0.4 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from two key issues: 1) The ErrorHandler.renderException
method used scopedErrors to determine debug mode instead of the application's actual debug configuration, causing stacktraces to be displayed in production. 2) The HtmlErrorRenderer.template
outputted exception properties (class, message, trace details) without HTML escaping, enabling XSS if exception messages contained user-controlled data. The commits fixed these by introducing a proper debug flag and adding escaping in the template rendering logic.