CVE-2020-11069: Typo3/cms core Backend Same-Site Request Forgery Vulnerability
HIGHCVE-2020-11069 is a HIGH (CVSS 8.0) backend same-site request forgery vulnerability (CWE-346: Origin Validation Error) affecting Typo3/cms core libraries in the Packagist ecosystem. The issue involves backend same-site request forgery in typo3 cms. Remediation is available by upgrading affected packages to version 9.5.17, 10.4.2.
CVE-2020-11069 at a Glance
Security Impact
CVSS: 8.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H).
How to Fix CVE-2020-11069
To remediate this vulnerability, upgrade all affected Typo3/cms core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade typo3/cms-core to 9.5.17
Upgrade typo3/cms-core to 10.4.2
Upgrade typo3/cms to 10.4.2
Upgrade typo3/cms to 9.5.17
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for typo3/cms-core
How to Check if You Are Affected
To determine whether your application is affected by CVE-2020-11069, inspect your project dependencies for Typo3/cms core:
inspect dependencies for typo3/cms-core
Analyze the terminal output to locate any version of Typo3/cms core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.5.17), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-346: Origin Validation Error, where the product does not properly verify that the source of data or communication is valid. In Typo3/cms core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2020-11069 Affected Typo3/cms core Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
typo3/cms-core
|
Packagist |
≥ 9.0.0
< 9.5.17
|
9.5.17
|
|
typo3/cms-core
|
Packagist |
≥ 10.0.0
< 10.4.2
|
10.4.2
|
|
typo3/cms
|
Packagist |
≥ 10.0.0
< 10.4.2
|
10.4.2
|
|
typo3/cms
|
Packagist |
≥ 9.0.0
< 9.5.17
|
9.5.17
|
References
Frequently Asked Questions
What is CVE-2020-11069?
Which Typo3/cms core versions are affected?
What version fixes CVE-2020-11069?
Is typo3/cms-core affected?
Is typo3/cms affected?
What is the CVSS score of CVE-2020-11069?
What CWE is associated with CVE-2020-11069?
How can I check Packagist dependencies for CVE-2020-11069?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pqg8-crx9-g8m4",
"modified" : "2024-02-05T11:13:08Z",
"published" : "2020-05-13T23:40:09Z",
"aliases" : [ "CVE-2020-11069" ],
"summary" : "Backend Same-Site Request Forgery in TYPO3 CMS",
"details" : "> ### Meta\n> * CVSS v3.1: AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C\n> * CWE-352\n> * CWE-346\n\n### Problem\nIt has been discovered that backend user interface and install tool are vulnerable to same-origin 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.\n\nIn 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-origin request forgery.\n\nMalicious payload such as HTML containing JavaScript might be provided by either an authenticated backend user or by a non-authenticated user using a 3rd party extension - e.g. file upload in a contact form with knowing the target location.\n\nThe attacked victim requires an active and valid backend or install tool user sessions at the time of the attack to be successful.\n\n### Solution\nUpdate to TYPO3 versions 9.5.17 or 10.4.2 that mitigates the problem described.\n\n### Additional Considerations\n\nThe deployment of additional mitigation techniques is suggested as described below.\n\n#### Sudo Mode Extension\n\nThis 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 by again by the acting user with providing their password again - this technique is known as \"sudo mode\". This way unintended actions happening in the background can be mitigated.\n\n* https://github.com/FriendsOfTYPO3/sudo-mode\n* https://extensions.typo3.org/extension/sudo_mode\n\n#### Content Security Policy\n\n[Content Security Policies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) tell (modern) browsers how resources served a particular site are handled - it also it 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/`.\n\n```\n# in fileadmin/.htaccess\n<IfModule mod_headers.c>\n\tHeader add Content-Security-Policy \"default-src 'self'; script-src 'none';\"\n</IfModule>\n```\n\n### Credits\nThanks to Matteo Bonaker who reported this issue and to TYPO3 security team member Oliver Hader who fixed the issue.\n\n### References\n* https://typo3.org/security/advisory/typo3-core-sa-2020-006",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "typo3/cms-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0"
}, {
"fixed" : "9.5.17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "typo3/cms-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "10.0.0"
}, {
"fixed" : "10.4.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "typo3/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "10.0.0"
}, {
"fixed" : "10.4.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "typo3/cms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "9.0.0"
}, {
"fixed" : "9.5.17"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-pqg8-crx9-g8m4"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-11069"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11069.yaml"
}, {
"type" : "WEB",
"url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11069.yaml"
}, {
"type" : "WEB",
"url" : "https://typo3.org/security/advisory/typo3-core-sa-2020-006"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-346", "CWE-352" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2020-05-13T23:38:41Z",
"nvd_published_at" : "2020-05-14T00:15:00Z"
}
}