Skip to content

Exceptions displayed in non-debug configurations in Symfony

Moderate severity GitHub Reviewed Published Mar 30, 2020 in symfony/symfony • Updated Feb 6, 2024

Package

composer symfony/error-handler (Composer)

Affected versions

>= 4.4.0, < 4.4.4
>= 5.0.0, < 5.0.4

Patched versions

4.4.4
5.0.4
composer symfony/symfony (Composer)
>= 4.4.0, < 4.4.4
>= 5.0.0, < 5.0.4
4.4.4
5.0.4

Description

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.

References

@nicolas-grekas nicolas-grekas published to symfony/symfony Mar 30, 2020
Reviewed Mar 30, 2020
Published to the GitHub Advisory Database Mar 30, 2020
Last updated Feb 6, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS score

0.058%
(25th percentile)

Weaknesses

CVE ID

CVE-2020-5274

GHSA ID

GHSA-m884-279h-32v2

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.