GHSA-r6mm-wmhf-849m json
Time-Based Information Disclosure Vulnerability in Flow
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist typo3/flow 2.3.16, 3.0.10, 3.1.7, 3.2.7, 3.3.5
Is GHSA-r6mm-wmhf-849m in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/flow | >=2.3.0, <2.3.16 >=3.0.0, <3.0.10 >=3.1.0, <3.1.7 >=3.2.0, <3.2.7 >=3.3.0, <3.3.5 |
2.3.16 3.0.10 3.1.7 3.2.7 3.3.5 |
References
Sources
- GitHub Advisory GHSA-r6mm-wmhf-849m
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.