GHSA-r6mm-wmhf-849m — typo3/flow
GHSA-r6mm-wmhf-849m is a security vulnerability in typo3/flow. A fix is available for typo3/flow — see the affected versions and patch details below.
Time-Based Information Disclosure Vulnerability in Flow
Real-World Exposure
typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/flow | ≥ 2.3.0&&< 2.3.16 | 2.3.16composer require typo3/flow:^2.3.16 |
| 🐘Packagist | typo3/flow | ≥ 3.0.0&&< 3.0.10 | 3.0.10composer require typo3/flow:^3.0.10 |
| 🐘Packagist | typo3/flow | ≥ 3.1.0&&< 3.1.7 | 3.1.7composer require typo3/flow:^3.1.7 |
| 🐘Packagist | typo3/flow | ≥ 3.2.0&&< 3.2.7 | 3.2.7composer require typo3/flow:^3.2.7 |
| 🐘Packagist | typo3/flow | ≥ 3.3.0&&< 3.3.5 | 3.3.5composer require typo3/flow:^3.3.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/flow to 2.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6mm-wmhf-849m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r6mm-wmhf-849m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r6mm-wmhf-849m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r6mm-wmhf-849m in your dependencies?
O3 Security finds GHSA-r6mm-wmhf-849m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.