{"answers":{"affected":"9 open source packages ship an affected version, including typo3/cms, typo3 and typo3/cms-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11069 in the wild and no public exploit code.","fix":"Upgrade typo3/cms to a fixed version for your release line: 10.4.2 or 9.5.17.","what":"CVE-2020-11069 is a high-severity vulnerability in Typo3 Typo3, published on 13 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-11069 and fix it if it is affected.\n\nWhat it is: CVE-2020-11069 is a high-severity vulnerability in Typo3 Typo3, published on 13 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-11069 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.2\n- typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.2\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.17\n- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.17\n- typo3 (Bitnami): affected from 9.0.0; fixed in 9.5.16, 10.4.1\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.2\n- typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.2\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.17\n- typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.17\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-2020-11069/ (Markdown: https://insights.sbomify.com/CVE-2020-11069/index.md)","id":"CVE-2020-11069","markdown":"https://insights.sbomify.com/CVE-2020-11069/index.md","name":"CVE-2020-11069","record":{"aliases":["BIT-typo3-2020-11069","GHSA-pqg8-crx9-g8m4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 CMS","requires_auth":"low_privilege","summary":"Attackers can trick authenticated backend users into executing malicious scripts, potentially creating new admin accounts and taking over the system.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"typo3","vendor":"typo3"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"},{"id":"CWE-346","name":"Origin Validation Error"}],"description":"In TYPO3 CMS 9.0.0 through 9.5.16 and 10.0.0 through 10.4.1, it has been discovered that the backend user interface and install tool are vulnerable to a same-site request forgery. A backend user can be tricked into interacting with a malicious resource an attacker previously managed to upload to the web server. Scripts are then executed with the privileges of the victims' user session. In a worst-case scenario, new admin users can be created which can directly be used by an attacker. The vulnerability is basically a cross-site request forgery (CSRF) triggered by a cross-site scripting vulnerability (XSS) - but happens on the same target host - thus, it's actually a same-site request forgery. Malicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a third party extension, e.g. file upload in a contact form with knowing the target location. To be successful, the attacked victim requires an active and valid backend or install tool user session at the time of the attack. This has been fixed in 9.5.17 and 10.4.2. The deployment of additional mitigation techniques is suggested as described below. - Sudo Mode Extension This TYPO3 extension intercepts modifications to security relevant database tables, e.g. those storing user accounts or storages of the file abstraction layer. Modifications need to confirmed again by the acting user providing their password again. This technique is known as sudo mode. This way, unintended actions happening in the background can be mitigated. - https://github.com/FriendsOfTYPO3/sudo-mode - https://extensions.typo3.org/extension/sudo_mode - Content Security Policy Content Security Policies tell (modern) browsers how resources served a particular site are handled. It is also possible to disallow script executions for specific locations. In a TYPO3 context, it is suggested to disallow direct script execution at least for locations /fileadmin/ and /uploads/.","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":"Cross-Site Request Forgery in TYPO3 CMS","id":"CVE-2020-11069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"typo3:typo3","products":["typo3:typo3"],"type":"csrf","year":"2020"},"n_packages":9,"n_references":1,"next":{"headline":"Cross-Site Scripting in SVG Sanitizer","id":"CVE-2020-11070"},"packages":[{"ecosystem":"Bitnami","fixed":["9.5.16","10.4.1"],"introduced":["9.0.0","10.0.0"],"last_affected":[],"package":"typo3","purl":"pkg:bitnami/typo3","source":"BIT-typo3-2020-11069"},{"ecosystem":"Packagist","fixed":["10.4.2"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["10.4.2"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["9.5.17"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":null,"source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["9.5.17"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms","purl":"pkg:composer/typo3/cms","source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["10.4.2"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["10.4.2"],"introduced":["10.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["9.5.17"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":null,"source":"GHSA-pqg8-crx9-g8m4"},{"ecosystem":"Packagist","fixed":["9.5.17"],"introduced":["9.0.0"],"last_affected":[],"package":"typo3/cms-core","purl":"pkg:composer/typo3/cms-core","source":"GHSA-pqg8-crx9-g8m4"}],"prev":{"headline":"Potential Buffer Overflow in LoRaMac-node","id":"CVE-2020-11068"},"products":["TYPO3 CMS"],"published":"2020-05-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["TYPO3"]},"summary":"Attackers can trick authenticated backend users into executing malicious scripts, potentially creating new admin accounts and taking over the system.","url":"https://insights.sbomify.com/CVE-2020-11069/"}