In affected versions of Sylius, exception messages from internal exceptions (like database exception) are wrapped by SymfonyComponentSecurityCoreExceptionAuthenticationServiceException and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer. A validation message with the exception details will be presented to the user when one will try to log into the shop. This has been patched in versions 1.3.14, 1.4.10, 1.5.7, and 1.6.3.
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 |
| Sylius |
Sylius |
* |
1.3.14 (excluding) |
| Sylius |
Sylius |
1.4.0 (including) |
1.4.10 (excluding) |
| Sylius |
Sylius |
1.5.0 (including) |
1.5.7 (excluding) |
| Sylius |
Sylius |
1.6.0 (including) |
1.6.3 (excluding) |
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