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
Weakness
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Symfony |
Sensiolabs |
4.4.0 (including) |
4.4.4 (excluding) |
| Symfony |
Sensiolabs |
5.0.0 (including) |
5.0.4 (excluding) |
| Symfony |
Ubuntu |
eoan |
* |
| Symfony |
Ubuntu |
trusty |
* |
| Symfony |
Ubuntu |
upstream |
* |
| Symfony |
Ubuntu |
xenial |
* |
Potential Mitigations
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
References