Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2013.1234 TYPO3-CORE-SA-2013-003: Incomplete Access Management and Remote Code Execution Vulnerability in TYPO3 Core 9 September 2013 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: TYPO3 Publisher: TYPO3 Operating System: UNIX variants (UNIX, Linux, OSX) Windows Impact/Access: Modify Arbitrary Files -- Existing Account Create Arbitrary Files -- Existing Account Access Confidential Data -- Existing Account Resolution: Patch/Upgrade Original Bulletin: http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-003/ - --------------------------BEGIN INCLUDED TEXT-------------------- TYPO3-CORE-SA-2013-003: Incomplete Access Management and Remote Code Execution Vulnerability in TYPO3 Core September 04, 2013 Category: TYPO3 Core Author: Helmut Hummel Keywords: Incomplete Access Management, Remote Code Execution It has been discovered that TYPO3 Core has Incomplete Access Management and is vulnerable to Remote Code Execution Component Type: TYPO3 Core Vulnerability Types: Cross-Site Scripting, Remote Code Execution Overall Severity: Critical Release Date: September 4, 2013 Vulnerable subcomponent: File handling / File Abstraction Layer Vulnerability Type: Incomplete Access Management Affected Versions: All versions from 6.0.0 up to the development branch of 6.2 Severity: Medium Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:P/I:P/A:N/E:F/RL:O/RC:C (What's that?) CVE: None assigned yet. Problem Description: TYPO3 comes with the possibility to restrict editors to certain file actions (copy, delete, move etc.) and to restrict these actions to be performed in certain locations (file mounts). This permission handling was only partly implemented with the introduction of the File Abstraction Layer (FAL). The file action permissions that can be set in backend user and group records were not respected and users could break out of file mounts by crafting URLs. Thus, unprivileged users could create or read arbitrary files within or outside the document root. Solution: Update to the TYPO3 version 6.0.9, 6.1.4 or the latest development version! It is important to clear all caches (clear cache all in the backend or deleting the complete typo3temp/Cache directory) for the changes to take effect after the TYPO3 source files have been updated! Notes: Administrators are advised to set file permissions for backend users or groups by using user TS Config instead of using the file permission check boxes in the user or group records. This allows more fine grained control for single file action permissions. Example for setting default permissions for users or groups in User TSConfig: permissions.file.default { addFile = 0 readFile = 1 writeFile = 1 copyFile = 1 moveFile = 1 renameFile = 0 unzipFile = 0 deleteFile = 0 addFolder = 1 readFolder = 1 writeFolder = 1 copyFolder = 1 moveFolder = 0 renameFolder = 0 deleteFolder = 1 recursivedeleteFolder = 1 } Example setting permissions for storage with ID 1 (overriding default settings): permissions.file.storage.1 { addFile = 1 readFile = 1 writeFile = 1 copyFile = 1 moveFile = 1 renameFile = 0 unzipFile = 0 deleteFile = 0 addFolder = 1 readFolder = 1 writeFolder = 1 copyFolder = 1 moveFolder = 0 renameFolder = 0 deleteFolder = 1 recursivedeleteFolder = 1 } Credits: Credits go to Sebastian Nerz who discovered and reported the issues, Steffen Ritter and Helmut Hummel for creating the fixes and Anja Leichsenring, Susanne Moog, Michiel Roos, Sascha Egerer and Ernesto Baschny for testing. Vulnerable subcomponent: File Abstraction Layer Vulnerability Type: Remote Code Execution Affected Versions: All versions from 6.0.0 up to the development branch of 6.2 Severity: Critical Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:F/RL:O/RC:C (What's that?) CVE: none assigned yet Problem Description: The check for denied file extensions implemented in the File Abstraction Layer as mentioned in advisory TYPO3-CORE-SA-2013-002 was incomplete. It was still possible for editors to rename files to have denied file extensions by inserting special characters that were removed at a later point. This (again) allowed authenticated editors to forge php files with arbitrary code, which can then be executed in web server's context. Solution: Update to the TYPO3 version 6.0.9, 6.1.4 or the latest development version! Credits: Credits go to Sascha Egerer who discovered and reported the issue. General Advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list. - --------------------------END INCLUDED TEXT-------------------- You have received this e-mail bulletin as a result of your organisation's registration with AusCERT. The mailing list you are subscribed to is maintained within your organisation, so if you do not wish to continue receiving these bulletins you should contact your local IT manager. If you do not know who that is, please send an email to auscert@auscert.org.au and we will forward your request to the appropriate person. NOTE: Third Party Rights This security bulletin is provided as a service to AusCERT's members. As AusCERT did not write the document quoted above, AusCERT has had no control over its content. The decision to follow or act on information or advice contained in this security bulletin is the responsibility of each user or organisation, and should be considered in accordance with your organisation's site policies and procedures. AusCERT takes no responsibility for consequences which may arise from following or acting on information or advice contained in this security bulletin. NOTE: This is only the original release of the security bulletin. It may not be updated when updates to the original are made. If downloading at a later date, it is recommended that the bulletin is retrieved directly from the author's website to ensure that the information is still current. Contact information for the authors of the original document is included in the Security Bulletin above. If you have any questions or need further information, please contact them directly. Previous advisories and external security bulletins can be retrieved from: http://www.auscert.org.au/render.html?cid=1980 =========================================================================== Australian Computer Emergency Response Team The University of Queensland Brisbane Qld 4072 Internet Email: auscert@auscert.org.au Facsimile: (07) 3365 7031 Telephone: (07) 3365 4417 (International: +61 7 3365 4417) AusCERT personnel answer during Queensland business hours which are GMT+10:00 (AEST). On call after hours for member emergencies only. =========================================================================== -----BEGIN PGP SIGNATURE----- Comment: http://www.auscert.org.au/render.html?it=1967 iQIVAwUBUi1AJxLndAQH1ShLAQLIrRAAhS+TLgIcELuKVK7CNU1IMoEIG0E9p7HN /1HfeD2g26g4osBs7bR7MmrP1kqL3sZGqw0tDg4fSIiro+RcdC3ibhAi5Qg0Gzti SLWIeQMkXurWep1itdWdBXuX0STDTz3yigyO0HTj8Y0GrV7EnwPyTbJGBznM/I5v zzYcqOVxSN1Uv6lvSZO6JEuJGX+0EPD6H+MtgMmiuMqsFIdWxJW+4VRbF3riezEm yCjGWsOI3uTSCO6ISWT/+7bK6HWI4UkK2m9iZ8RERADfzY4MIlppEfTNjPGQUIIK yo5guhzuB8lP5HLYJHggdmKkxxazeUoUu9bzzEPxQ1tI+ZjsZDct9TDMHtmQ3fUO QRndaUw3zZ8+U69FG4hjfigbHh/2+KabA9bAO+e1WRfc//RjEFx9AHZ4l1JQPaCX fZp3jHoHM4Sg4bpGiCVNQ/bb8Iter2fdUyDfV5fDtW1xFepjAOzvratcL4S5dWL/ 3DrMVFG3OyZvdVFT9hjQqyYoMQp0T2lNBz7mzD52w0e8DJLc5COd1XMqOPybBm20 qvQYvkqHckTucrrATWnPGx20en5iUyRjux1NrIPJYMKyHHyflNSUuIuAogWxtc5I R4GVm1DNIUpVpJHqbM1aF7SYEQkosZZD9GnDWYdbZ2nFE7wwMjVwfhB0jWVirr7J d1j4W+D642E= =gAZF -----END PGP SIGNATURE-----