GHSA-6pq8-67pw-j6hw Time-Based Information Disclosure Vulnerability in Flow
Not scored
Published
Check this codebase for GHSA-6pq8-67pw-j6hw and fix it if it is affected.
What it is: GHSA-6pq8-67pw-j6hw is a vulnerability in neos/flow, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-6pq8-67pw-j6hw in the wild and no public exploit code.
Affected packages and fixed versions:
- neos/flow (Packagist): affected from 2.3.0; fixed in 2.3.16
- neos/flow (Packagist): affected from 2.3.0; fixed in 2.3.16
- neos/flow (Packagist): affected from 3.0.0; fixed in 3.0.10
- neos/flow (Packagist): affected from 3.0.0; fixed in 3.0.10
- neos/flow (Packagist): affected from 3.1.0; fixed in 3.1.7
- neos/flow (Packagist): affected from 3.1.0; fixed in 3.1.7
- neos/flow (Packagist): affected from 3.2.0; fixed in 3.2.7
- neos/flow (Packagist): affected from 3.2.0; fixed in 3.2.7
- neos/flow (Packagist): affected from 3.3.0; fixed in 3.3.5
- neos/flow (Packagist): affected from 3.3.0; fixed in 3.3.5
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-6pq8-67pw-j6hw/ (Markdown: https://insights.sbomify.com/GHSA-6pq8-67pw-j6hw/index.md)
Attackers can determine if user accounts exist by measuring response times during login attempts due to conditional password hashing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-6pq8-67pw-j6hw?
GHSA-6pq8-67pw-j6hw is a vulnerability in neos/flow, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by GHSA-6pq8-67pw-j6hw?
10 open source packages ship an affected version, including neos/flow.
| Package | Affected | Fixed in |
|---|---|---|
neos/flow Packagist | From 2.3.0 | 2.3.16 |
neos/flow Packagist | From 2.3.0 | 2.3.16 |
neos/flow Packagist | From 3.0.0 | 3.0.10 |
neos/flow Packagist | From 3.0.0 | 3.0.10 |
neos/flow Packagist | From 3.1.0 | 3.1.7 |
neos/flow Packagist | From 3.1.0 | 3.1.7 |
4 more packages
neos/flow Packagist | From 3.2.0 | 3.2.7 |
neos/flow Packagist | From 3.2.0 | 3.2.7 |
neos/flow Packagist | From 3.3.0 | 3.3.5 |
neos/flow Packagist | From 3.3.0 | 3.3.5 |
How do I fix GHSA-6pq8-67pw-j6hw?
Upgrade neos/flow to a fixed version for your release line: 2.3.16, 3.0.10, 3.1.7 or 3.2.7.
Is GHSA-6pq8-67pw-j6hw being exploited?
There is no known exploitation of GHSA-6pq8-67pw-j6hw in the wild and no public exploit code.