Skip to content

Sulu Observable Response Discrepancy on Admin Login

Moderate severity GitHub Reviewed Published Aug 3, 2023 in sulu/sulu • Updated Nov 10, 2023

Package

composer sulu/sulu (Composer)

Affected versions

>= 2.5.0, < 2.5.10

Patched versions

2.5.10

Description

Impact

It allows over the Admin Login form to detect which user (username, email) exists and which one do not exist.

Impacted by this issue are Sulu installation >= 2.5.0 and <2.5.10 using the newer Symfony Security System which is default since Symfony 6.0 but can be enabled in Symfony 5.4. Sulu Installation not using the old Symfony 5.4 security System and previous version are not impacted by this Security issue.

Patches

The problem has been patched in version 2.5.10.

Workarounds

Create a custom AuthenticationFailureHandler which does not return the $exception->getMessage(); instead the $exception->getMessageKey();

References

Currently no references.

References

@alexander-schranz alexander-schranz published to sulu/sulu Aug 3, 2023
Published to the GitHub Advisory Database Aug 3, 2023
Reviewed Aug 3, 2023
Published by the National Vulnerability Database Aug 4, 2023
Last updated Nov 10, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.106%
(44th percentile)

Weaknesses

CVE ID

CVE-2023-39343

GHSA ID

GHSA-wmwf-49vv-p3mr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.