{"answers":{"affected":"15 open source packages ship an affected version, including typo3/cms-core, typo3 and typo3/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36105 in the wild and no public exploit code.","fix":"Upgrade typo3/cms-core to a fixed version for your release line: 10.4.32, 11.5.16, 7.6.58 or 8.7.48.","what":"CVE-2022-36105 is a medium-severity vulnerability in Typo3 Typo3, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36105 and fix it if it is affected.\n\nWhat it is: CVE-2022-36105 is a medium-severity vulnerability in Typo3 Typo3, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36105 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.32\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.32\n- typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.16\n- typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.16\n- typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.58\n- typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.58\n- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.48\n- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.48\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.37\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.37\n- typo3 (Bitnami): affected from 7.0.0; fixed in 7.6.57, 8.7.47, 9.5.36, 10.4.31, 11.5.15\n- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.32\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/CVE-2022-36105/ (Markdown: https://insights.sbomify.com/CVE-2022-36105/index.md)","id":"CVE-2022-36105","markdown":"https://insights.sbomify.com/CVE-2022-36105/index.md","name":"CVE-2022-36105","record":{"aliases":["BIT-typo3-2022-36105","GHSA-m392-235j-9r7r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"none","summary":"Attackers can enumerate valid user accounts by analyzing response timing during authentication in TYPO3.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"TYPO3 is an open source PHP based web content management system released under the GNU GPL. It has been discovered that observing response time during user authentication (backend and frontend) can be used to distinguish between existing and non-existing user accounts. Extension authors of 3rd party TYPO3 extensions providing a custom authentication service should check if the extension is affected by the described problem. Affected extensions must implement new `MimicServiceInterface::mimicAuthUser`, which simulates corresponding times regular processing would usually take. Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix this problem. There are no known workarounds for this issue.","ecosystems":["Bitnami","Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"User Enumeration via Response Timing in TYPO3","id":"CVE-2022-36105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"typo3:typo3","products":["typo3:typo3"],"type":"information_disclosure","year":"2022"},"n_packages":15,"n_references":3,"next":{"headline":"Missing check for expiration time of password reset token in TYPO3","id":"CVE-2022-36106"},"packages":[{"ecosystem":"Bitnami","fixed":["7.6.57","8.7.47","9.5.36","10.4.31","11.5.15"],"introduced":["7.0.0","8.0.0","9.0.0","10.0.0","11.0.0"],"last_affected":[],"package":"typo3","purl":"pkg:bitnami/typo3","source":"BIT-typo3-2022-36105"},{"ecosystem":"Packagist","fixed":["10.4.32"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["10.4.32"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["11.5.16"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["11.5.16"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["10.4.32"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["10.4.32"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["11.5.16"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["11.5.16"],"introduced":["11.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["7.6.58"],"introduced":["7.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["7.6.58"],"introduced":["7.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["8.7.48"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["8.7.48"],"introduced":["8.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["9.5.37"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-m392-235j-9r7r"},{"ecosystem":"Packagist","fixed":["9.5.37"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-m392-235j-9r7r"}],"prev":{"headline":"Denial of Service via Page Error Handling in TYPO3/cms","id":"CVE-2022-36104"},"products":["typo3"],"published":"2022-09-13","related":[{"cvss_score":10,"headline":"Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection","id":"CVE-2009-0258","kev_date_added":null,"published":"2009-01-22"},{"cvss_score":9.8,"headline":"Typo3 SQL injection due to faulty prepared statements","id":"CVE-2011-3583","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":9.8,"headline":"Typo3 Authentication Bypass","id":"CVE-2011-4628","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":8.8,"headline":"Persisted Cross-Site Scripting in Frontend Rendering in typo3","id":"CVE-2023-24814","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":8.8,"headline":"Cross-Site-Request-Forgery in Backend URI Handling in Typo3","id":"CVE-2021-41113","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":8.8,"headline":"Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS","id":"CVE-2020-15098","kev_date_added":null,"published":"2020-07-29"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in TYPO3 CMS","id":"CVE-2020-11067","kev_date_added":null,"published":"2020-05-13"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["TYPO3"]},"summary":"Attackers can enumerate valid user accounts by analyzing response timing during authentication in TYPO3.","url":"https://insights.sbomify.com/CVE-2022-36105/"}