CVE-2020-15132: Sulu/sulu Reset Password / Login Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-wfm4-pq59-wg6r
CVSS 5.3
CWE-209
Published
Advisory Summary

CVE-2020-15132 is a MODERATE (CVSS 5.3) reset password / login vulnerability vulnerability (CWE-209: Generation of Error Message Containing Sensitive Information) affecting Sulu/sulu libraries in the Packagist ecosystem. The issue involves reset password / login vulnerability in sulu. Remediation is available by upgrading affected packages to version 1.6.34, 2.0.10, 2.1.1.

CVE-2020-15132 at a Glance

CVE Identifier CVE-2020-15132
GHSA Identifier GHSA-wfm4-pq59-wg6r
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-209: Generation of Error Message Containing Sensitive Information
Affected Product Sulu/sulu
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2020-15132

To remediate this vulnerability, upgrade all affected Sulu/sulu dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

sulu/sulu fixed: 1.6.34
Upgrade sulu/sulu to 1.6.34
sulu/sulu fixed: 2.0.10
Upgrade sulu/sulu to 2.0.10
sulu/sulu fixed: 2.1.1
Upgrade sulu/sulu to 2.1.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for sulu/sulu

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-15132, inspect your project dependencies for Sulu/sulu:

inspect dependencies for sulu/sulu

Analyze the terminal output to locate any version of Sulu/sulu in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.6.34), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-209: Generation of Error Message Containing Sensitive Information, where the product generates an error message that includes sensitive information about its environment, users, or associated data. In Sulu/sulu, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact _What kind of vulnerability is it? Who is impacted?_ 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: ```json { "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: ```json {"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. ### Patches This problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1. ### Workarounds Override the files manually in your project and change them accordingly.

CVE-2020-15132 Affected Sulu/sulu Versions

3 component(s)
Fixed Versions:
1.6.342.0.102.1.1
Product / Package Ecosystem Affected Versions Fixed Version
sulu/sulu
Packagist
< 1.6.34
1.6.34
sulu/sulu
Packagist
≥ 2.0.0
< 2.0.10
2.0.10
sulu/sulu
Packagist
≥ 2.1.0
< 2.1.1
2.1.1

References

Frequently Asked Questions

What is CVE-2020-15132?
CVE-2020-15132 is a security vulnerability in Sulu/sulu involving Reset Password / Login vulnerability in Sulu under CWE-209: Generation of Error Message Containing Sensitive Information.
Which Sulu/sulu versions are affected?
Affected versions include releases prior to 1.6.34, 2.0.10, 2.1.1 across affected packages: sulu/sulu.
What version fixes CVE-2020-15132?
Upgrading to 1.6.34, 2.0.10, 2.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is sulu/sulu affected?
Yes, sulu/sulu is affected in releases prior to 1.6.34, 2.0.10, 2.1.1. Upgrade your dependency to 1.6.34, 2.0.10, 2.1.1 or later.
What is the CVSS score of CVE-2020-15132?
CVE-2020-15132 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2020-15132?
CVE-2020-15132 is classified under CWE-209: Generation of Error Message Containing Sensitive Information (The product generates an error message that includes sensitive information about its environment, users, or associated data.).
How can I check Packagist dependencies for CVE-2020-15132?
Run the dependency tree command: 'inspect dependencies for sulu/sulu'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wfm4-pq59-wg6r",
  "modified" : "2021-01-07T23:41:55Z",
  "published" : "2020-08-05T21:27:44Z",
  "aliases" : [ "CVE-2020-15132" ],
  "summary" : "Reset Password / Login vulnerability in Sulu",
  "details" : "### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nThis vulnerability consists of a few related issues:\n\n#### Forget password leaks information if the user exists\n\nWhen 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:\n\n```json\n{\n    \"code\": 0,\n    \"message\": \"Entity with the type \\u0022Sulu\\\\Bundle\\\\SecurityBundle\\\\Entity\\\\User\\u0022 and the id \\u0022asdf\\u0022 not found.\"\n}\n```\n\nThis enables attackers to retrieve valid usernames.\n\n#### Forgot password leaks user email if user exists\n\nThe response of the \"Forgot Password\" request returns the email address to which the email was sent, if the operation was successful:\n\n```json\n{\"email\":\"admin@localhost.local\"}\n```\n\nThis information should not be exposed, as it can be used to gather email addresses.\n\n#### Response time of login gives hint if the username exists\n\nIf 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.\n\n#### Reset Token for Forgot Password feature is not hashed\n\nThe 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.\n\n### Patches\n\nThis problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1.\n\n### Workarounds\n\nOverride the files manually in your project and change them accordingly.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sulu/sulu"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.6.34"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sulu/sulu"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.0.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "sulu/sulu"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.1.0"
      }, {
        "fixed" : "2.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/security/advisories/GHSA-wfm4-pq59-wg6r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-15132"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sulu/sulu/commit/0fbb6009eb6a8efe63b7e3f3b4b886dc54bb2326"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-209" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-05T21:26:26Z",
    "nvd_published_at" : null
  }
}