GitHub Advisoryadvisory · Packagist

GHSA-m884-279h-32v2 Exceptions displayed in non-debug configurations in Symfony

MEDIUM Published 2020-03-30 Modified 2024-02-06 Official page ↗
Aliases
CVE-2020-5274
Ecosystem
Packagist
Packages
symfony/error-handler, symfony/symfony
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Weaknesses
CWE-209
Reviewed
2020-03-30

Affected packages

• Packagist symfony/error-handler: >= 4.4.0, < 4.4.4 → fixed in 4.4.4 • Packagist symfony/error-handler: >= 5.0.0, < 5.0.4 → fixed in 5.0.4 • Packagist symfony/symfony: >= 4.4.0, < 4.4.4 → fixed in 4.4.4 • Packagist symfony/symfony: >= 5.0.0, < 5.0.4 → fixed in 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.

Related

Alias · CVE (1)

  • CVE-2020-5274 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… vulnerability

Weakness · CWE (1)

  • CWE-209 Generation of Error Message Containing Sensitive Information weakness

References