symfony/error-handler
Affected
- introduced
4.4.0, fixed4.4.4(ecosystem)
Fixed versions
4.4.4
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-symfony-2020-5274, CVE-2020-5274
Exceptions displayed in non-debug configurations in Symfony
Description
-----------
When ErrorHandler renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-debug environments.
Resolution
----------
The ErrorHandler class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-debug environments.
The patches for this issue are available here and here for branch 4.4.
Credits
-------
I would like to thank Luka Sikic for reporting & Yonel Ceruto and Jérémy Derussé for fixing the issue.
Medium Basis: The source's own band: MODERATE
4.4.0, fixed 4.4.4 (ecosystem)4.4.4
The export has no generic command for this ecosystem.
5.0.0, fixed 5.0.4 (ecosystem)5.0.4
The export has no generic command for this ecosystem.
4.4.0, fixed 4.4.4 (ecosystem)4.4.4
The export has no generic command for this ecosystem.
5.0.0, fixed 5.0.4 (ecosystem)5.0.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0