GHSA-6pq8-67pw-j6hw
MEDIUMTime-Based Information Disclosure Vulnerability in Flow
Blast Radius
neos/flow🐘neos/flow🐘neos/flow🐘neos/flow🐘neos/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 | neos/flow | ≥ 2.3.0&&< 2.3.16 | 2.3.16 |
| 🐘Packagist | neos/flow | ≥ 3.0.0&&< 3.0.10 | 3.0.10 |
| 🐘Packagist | neos/flow | ≥ 3.1.0&&< 3.1.7 | 3.1.7 |
| 🐘Packagist | neos/flow | ≥ 3.2.0&&< 3.2.7 | 3.2.7 |
| 🐘Packagist | neos/flow | ≥ 3.3.0&&< 3.3.5 | 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 neos/flow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update neos/flow to 2.3.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6pq8-67pw-j6hw 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 pinpoints whether GHSA-6pq8-67pw-j6hw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6pq8-67pw-j6hw. 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-6pq8-67pw-j6hw in your dependencies?
O3 detects GHSA-6pq8-67pw-j6hw across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.