Information Exposure Affecting sulu/sulu package, versions <1.6.35>=2.0.0, <2.0.10>=2.1.0, <2.1.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PHP-SULUSULU-597470
- published6 Aug 2020
- disclosed6 Aug 2020
- creditUnknown
Introduced: 6 Aug 2020
CVE-2020-15132 (opens in a new tab)How to fix?
Upgrade sulu/sulu to version 1.6.35, 2.0.10, 2.1.1 or higher.
Overview
sulu/sulu is a highly extensible open-source PHP content management system based on the Symfony framework.
Affected versions of this package are vulnerable to Information Exposure. This vulnerability consists of a few related issues:
Forget password leaks information if the user exists
When the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a 400 error code is returned, along with a error message saying that this user name does not exist:
{
"code": 0,
"message": "Entity with the type \u0022Sulu\\Bundle\\SecurityBundle\\Entity\\User\u0022 and the id \u0022asdf\u0022 not found."
}
This enables attackers to retrieve valid usernames.
#
Forgot password leaks user email if user exists
The response of the "Forgot Password" request returns the email address to which the email was sent, if the operation was successful:
{"email":"admin@localhost.local"}
This information should not be exposed, as it can be used to gather email addresses.
#
Response time of login gives hint if the username exists
If the username the user enters in the login screen does not exists, the request responds much faster than if the username exists. This again allows attackers to retrieve valid usernames.
#
Reset Token for Forgot Password feature is not hashed
The reset token in the user database table is not hashed. That means that somebody could try to request a new password using the Forgot Password feature, and look that up in the database, if the attacker somehow got access to the database. Hashing the reset token would fix that problem.