PHP/sulu/sulu/1.5.19

GHSA-6h7h-m7p5-hjqp

Sulu checks fix permissions for subentities endpoints

Impact

A user which has permission for the Sulu Admin via atleast one role could have access to the subentities of contacts via the admin API without even have permission for contacts.

Patches

The issue was patched in release 2.6.22 and 3.0.5.

Workarounds

Create a Symfony Request Listener checking the permissions for the specific roles.

Resources

Github Advisory: https://github.com/sulu/sulu/security/advisories/GHSA-6h7h-m7p5-hjqp

GHSA-gm2x-6475-g9r8

XSS Injection in Media Collection Title was possible

Impact

A logged in admin user was possible to add a script injection (XSS) in the collection title which was executed.

Workarounds

Manual patching the js files.

For more information

If you have any questions or comments about this advisory:'

• Email us at security@sulu.io

GHSA-h58v-g3q6-q9fx

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in sulu/sulu

Impact

What kind of vulnerability is it? Who is impacted?

It is an issue when input HTML into the Tag name. The HTML is execute when the tag name is listed in the auto complete form. Only admin users are affected and only admin users can create tags.

Patches

Has the problem been patched? What versions should users upgrade to?

The problem is patched with Version 1.6.42.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Create a custom request listener to avoid that this kind of tags are created.

References

Are there any links users can visit to find out more?

Currently not.

For more information

If you have any questions or comments about this advisory:

• Open an issue in sulu/sulu repository
• Email us at security@sulu.io

GHSA-vx6j-pjrh-vgjh

PHP file inclusion in the Sulu admin panel

Impact

What kind of vulnerability is it? Who is impacted?

An attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.

• Compromised components: Arbitrary file read on the server, (Potential) Remote code execution
• Exploitation pre-requisite: User account on the backend

Patches

Has the problem been patched? What versions should users upgrade to?

The problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Overwrite the service sulu_route.generator.expression_token_provider and wrap the translator before passing it to the expression language.

References

Are there any links users can visit to find out more?

Currently not.

For more information

If you have any questions or comments about this advisory: * Open an issue in example link to repo * Email us at example email address

GHSA-wfm4-pq59-wg6r

Reset Password / Login vulnerability in Sulu

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:

{
    "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.

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.