{"answers":{"affected":"10 open source packages ship an affected version, including typo3/flow.","exploited":"There is no known exploitation of GHSA-r6mm-wmhf-849m in the wild and no public exploit code.","fix":"Upgrade typo3/flow to a fixed version for your release line: 2.3.16, 3.0.10, 3.1.7 or 3.2.7.","what":"GHSA-r6mm-wmhf-849m is a vulnerability in typo3/flow, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-r6mm-wmhf-849m and fix it if it is affected.\n\nWhat it is: GHSA-r6mm-wmhf-849m is a vulnerability in typo3/flow, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-r6mm-wmhf-849m in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/flow (Packagist): affected from 2.3.0; fixed in 2.3.16\n- typo3/flow (Packagist): affected from 2.3.0; fixed in 2.3.16\n- typo3/flow (Packagist): affected from 3.0.0; fixed in 3.0.10\n- typo3/flow (Packagist): affected from 3.0.0; fixed in 3.0.10\n- typo3/flow (Packagist): affected from 3.1.0; fixed in 3.1.7\n- typo3/flow (Packagist): affected from 3.1.0; fixed in 3.1.7\n- typo3/flow (Packagist): affected from 3.2.0; fixed in 3.2.7\n- typo3/flow (Packagist): affected from 3.2.0; fixed in 3.2.7\n- typo3/flow (Packagist): affected from 3.3.0; fixed in 3.3.5\n- typo3/flow (Packagist): affected from 3.3.0; fixed in 3.3.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-r6mm-wmhf-849m/ (Markdown: https://insights.sbomify.com/GHSA-r6mm-wmhf-849m/index.md)","id":"GHSA-r6mm-wmhf-849m","markdown":"https://insights.sbomify.com/GHSA-r6mm-wmhf-849m/index.md","name":"GHSA-r6mm-wmhf-849m","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Flow authentication provider","requires_auth":"none","summary":"Attackers can determine if user accounts exist via timing attacks on password hashing, requiring a patch to ensure constant-time comparison.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Time-Based Information Disclosure Vulnerability in Flow","id":"GHSA-r6mm-wmhf-849m","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":10,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.3.16"],"introduced":["2.3.0"],"last_affected":[],"package":"typo3/flow","purl":null,"source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["2.3.16"],"introduced":["2.3.0"],"last_affected":[],"package":"typo3/flow","purl":"pkg:composer/typo3/flow","source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.0.10"],"introduced":["3.0.0"],"last_affected":[],"package":"typo3/flow","purl":null,"source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.0.10"],"introduced":["3.0.0"],"last_affected":[],"package":"typo3/flow","purl":"pkg:composer/typo3/flow","source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.1.7"],"introduced":["3.1.0"],"last_affected":[],"package":"typo3/flow","purl":null,"source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.1.7"],"introduced":["3.1.0"],"last_affected":[],"package":"typo3/flow","purl":"pkg:composer/typo3/flow","source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.2.7"],"introduced":["3.2.0"],"last_affected":[],"package":"typo3/flow","purl":null,"source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.2.7"],"introduced":["3.2.0"],"last_affected":[],"package":"typo3/flow","purl":"pkg:composer/typo3/flow","source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.3.5"],"introduced":["3.3.0"],"last_affected":[],"package":"typo3/flow","purl":null,"source":"GHSA-r6mm-wmhf-849m"},{"ecosystem":"Packagist","fixed":["3.3.5"],"introduced":["3.3.0"],"last_affected":[],"package":"typo3/flow","purl":"pkg:composer/typo3/flow","source":"GHSA-r6mm-wmhf-849m"}],"products":null,"published":"2024-06-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can determine if user accounts exist via timing attacks on password hashing, requiring a patch to ensure constant-time comparison.","url":"https://insights.sbomify.com/GHSA-r6mm-wmhf-849m/"}