Skip to content

Contao: Remember-me tokens will not be cleared after a password change

Moderate severity GitHub Reviewed Published Apr 9, 2024 in contao/contao • Updated Apr 9, 2024

Package

composer contao/core-bundle (Composer)

Affected versions

< 4.13.40

Patched versions

4.13.40

Description

Impact

When a front end member changes their password, the corresponding remember-me tokens are not removed.

Patches

Update to Contao 4.13.40.

Workarounds

Disable "Allow auto login" in the login module.

References

https://contao.org/en/security-advisories/remember-me-tokens-are-not-cleared-after-a-password-change

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

References

@leofeyer leofeyer published to contao/contao Apr 9, 2024
Published to the GitHub Advisory Database Apr 9, 2024
Reviewed Apr 9, 2024
Published by the National Vulnerability Database Apr 9, 2024
Last updated Apr 9, 2024

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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
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:H/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-30262

GHSA ID

GHSA-r4r6-j2j3-7pp5

Source code

Credits

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