GHSA-6pq8-67pw-j6hw: Time-Based Information Disclosure Vulnerability in Flow
The PersistedUsernamePasswordProvider was prone to a information disclosure of account existance based on timing attacks as the hashing of passwords was only done in case an account was found. We changed the core so that the provider always does a password comparison in case credentials were submitted at all.
Published May 17, 2024
Affected packages
neos/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.3.0, < 2.3.16
- Fixed in
- 2.3.16
- Check
composer show neos/flow
neos/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.0.10
- Fixed in
- 3.0.10
- Check
composer show neos/flow
neos/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.1.0, < 3.1.7
- Fixed in
- 3.1.7
- Check
composer show neos/flow
neos/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.0, < 3.2.7
- Fixed in
- 3.2.7
- Check
composer show neos/flow
neos/flow
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.0, < 3.3.5
- Fixed in
- 3.3.5
- Check
composer show neos/flow
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
The PersistedUsernamePasswordProvider was prone to a information disclosure of account existance based on timing attacks as the hashing of passwords was only done in case an account was found. We changed the core so that the provider always does a password comparison in case credentials were submitted at all.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
