Exceptions displayed in non-debug configurations in Symfony
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/error-handler Packagist |
|
|
| symfony/symfony Packagist |
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/error-handler Packagist |
|
|
| symfony/symfony Packagist |
|
|
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 stacktrace. In addition, the stacktrace were displayed even in a non-debug configuration. The ErrorHandler now escape alls properties of the exception, and the stacktrace is only display in debug configuration. This issue is patched in symfony/http-foundation versions 4.4.5 and 5.0.5
From the CVE record · GitHub_M
Symfony ErrorHandler did not properly escape some exception properties when rendering a stack trace, and it displayed stack traces even when debug mode was off. This could expose exception details; the input does not specify whether exploitation requires authentication or user interaction.
Teams running symfony/error-handler or symfony/symfony versions 4.4.0–4.4.3 or 5.0.0–5.0.3 should check their installations.