{"answers":{"affected":"2 open source packages ship an affected version, including typo3/cms.","exploited":"There is no known exploitation of GHSA-mh3r-6cp5-hc2j in the wild and no public exploit code.","fix":"Upgrade typo3/cms to 8.6.1 or later.","what":"GHSA-mh3r-6cp5-hc2j is an authentication bypass vulnerability in typo3/cms, 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-mh3r-6cp5-hc2j and fix it if it is affected.\n\nWhat it is: GHSA-mh3r-6cp5-hc2j is an authentication bypass vulnerability in typo3/cms, 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-mh3r-6cp5-hc2j in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 8.2.0; fixed in 8.6.1\n- typo3/cms (Packagist): affected from 8.2.0; fixed in 8.6.1\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-mh3r-6cp5-hc2j/ (Markdown: https://insights.sbomify.com/GHSA-mh3r-6cp5-hc2j/index.md)","id":"GHSA-mh3r-6cp5-hc2j","markdown":"https://insights.sbomify.com/GHSA-mh3r-6cp5-hc2j/index.md","name":"GHSA-mh3r-6cp5-hc2j","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Attackers can bypass authentication restrictions to log in as disabled frontend users in TYPO3 due to late TCA initialization.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Due to late TCA initialization the authentication service fails to restrict frontend user according to the validation rules. Therefore it is possible to authenticate restricted (e.g. disabled) frontend users.","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":"Authentication Bypass in TYPO3 Frontend","id":"GHSA-mh3r-6cp5-hc2j","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["8.6.1"],"introduced":["8.2.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-mh3r-6cp5-hc2j"},{"ecosystem":"Packagist","fixed":["8.6.1"],"introduced":["8.2.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-mh3r-6cp5-hc2j"}],"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 bypass authentication restrictions to log in as disabled frontend users in TYPO3 due to late TCA initialization.","url":"https://insights.sbomify.com/GHSA-mh3r-6cp5-hc2j/"}