How severe is GHSA-r6mm-wmhf-849m?

No CVSS score has been assigned to GHSA-r6mm-wmhf-849m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r6mm-wmhf-849m?

GHSA-r6mm-wmhf-849m affects the following packages: typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-r6mm-wmhf-849m?

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.

How do I detect GHSA-r6mm-wmhf-849m in my Packagist dependencies?

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.

How do I mitigate GHSA-r6mm-wmhf-849m if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-r6mm-wmhf-849m actively exploited in the wild?

No public exploit code has been indexed for GHSA-r6mm-wmhf-849m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r6mm-wmhf-849m published, and has it been updated?

GHSA-r6mm-wmhf-849m was published on June 5, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Time-Based Information Disclosure Vulnerability in Flow

Real-World Exposure

5 pkgs affected

🐘typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flow

Real-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

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/flow`	≥ 2.3.0&&< 2.3.16	2.3.16`composer require typo3/flow:^2.3.16`
🐘Packagist	`typo3/flow`	≥ 3.0.0&&< 3.0.10	3.0.10`composer require typo3/flow:^3.0.10`
🐘Packagist	`typo3/flow`	≥ 3.1.0&&< 3.1.7	3.1.7`composer require typo3/flow:^3.1.7`
🐘Packagist	`typo3/flow`	≥ 3.2.0&&< 3.2.7	3.2.7`composer require typo3/flow:^3.2.7`
🐘Packagist	`typo3/flow`	≥ 3.3.0&&< 3.3.5	3.3.5`composer require typo3/flow:^3.3.5`

Detection & mitigation playbook

Open-source dependency

Detect
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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-r6mm-wmhf-849m in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Time-Based Information Disclosure Vulnerability in FlowGHSA-r6mm-wmhf-849m