Advisory

GHSA-m884-279h-32v2

Also known as: BIT-symfony-2020-5274, CVE-2020-5274

Summary

Exceptions displayed in non-debug configurations in Symfony

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-03-30 20:09 UTC
Modified
2026-09-10 03:48 UTC

Affected packages and fixes

symfony/error-handler

Packagist · All systems

Affected

  • introduced 4.4.0, fixed 4.4.4 (ecosystem)

Fixed versions

4.4.4

Fix

The export has no generic command for this ecosystem.

symfony/error-handler

Packagist · All systems

Affected

  • introduced 5.0.0, fixed 5.0.4 (ecosystem)

Fixed versions

5.0.4

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 4.4.0, fixed 4.4.4 (ecosystem)

Fixed versions

4.4.4

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 5.0.0, fixed 5.0.4 (ecosystem)

Fixed versions

5.0.4

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences