Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2016.1782
Multiple vulnerabilities have been identified in TYPO3
20 July 2016
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: TYPO3
Publisher: TYPO3
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Execute Arbitrary Code/Commands -- Existing Account
Cross-site Scripting -- Remote with User Interaction
Provide Misleading Information -- Remote/Unauthenticated
Access Confidential Data -- Remote/Unauthenticated
Unauthorised Access -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2016-5385
Reference: ESB-2016.1764
Original Bulletin:
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-014
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-015
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-016
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-017
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-018
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-019
https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-020
Comment: This bulletin contains seven (7) TYPO3 security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
TYPO3-CORE-SA-2016-014: Cross-Site Scripting in TYPO3 Backend
July 19, 2016
Category: TYPO3 CMS
Author: Nicole Cordes
Keywords: Backend, Cross-Site Scripting, XSS
It has been discovered, that TYPO3 is susceptible to Cross-Site Scripting.
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerable subcomponent: Backend
Vulnerability Type: Cross-Site Scripting
Affected Versions: Versions 6.2.0 to 6.2.25, 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0
Severity: Medium
Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:P/I:P/A:N/E:P/RL:O/RC:C
CVE: not assigned yet
Problem Description: Failing to properly encode user input, some backend
components are vulnerable to Cross-Site Scripting. A valid backend user account
is needed to exploit this vulnerability.
Solution: Update to TYPO3 versions 6.2.26, 7.6.10 or 8.2.1 that fix the problem
described.
Credits: Thanks to Falk Huber, Markus Bucher, Martin Heigermoser and Nicole
Cordes who discovered and reported the issues.
General Advice: Follow the recommendations that are given in the TYPO3 Security
Guide. Please subscribe to the typo3-announce mailing list.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-015: Insecure Unserialize in TYPO3 Import/Export
July 19, 2016
Category: TYPO3 CMS
Author: Nicole Cordes
Keywords: Core, Insecure Unserialize
It has been discovered, that TYPO3 is susceptible to Insecure Unserialize.
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerable subcomponent: Import/Export
Vulnerability Type: Insecure Unserialize
Affected Versions: Versions 6.2.0 to 6.2.25, 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0
Severity: Medium
Suggested CVSS v2.0: AV:N/AC:H/Au:S/C:P/I:P/A:P/E:P/RL:O/RC:C
CVE: not assigned yet
Problem Description: Failing to properly validate incoming import data, the
Import/Export component is susceptible to insecure unserialize. To exploit this
vulnerability a valid backend user account is needed.
Solution: In the released TYPO3 versions 6.2.26, 7.6.10 or 8.2.1 the
Import/Export module is disabled by default for non-admin users. To re-activate
the Import/Export module for trusted users, please add
"options.impexp.enableImportForNonAdminUser = 1" to the users TSconfig.
Credits: Thanks to Franz Jahn 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.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-016: SQL Injection in TYPO3 Frontend Login
July 19, 2016
Category: TYPO3 CMS
Author: Nicole Cordes
Keywords: Frontend, Login, SQL Injection
It has been discovered, that TYPO3 is susceptible to SQL Injection.
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerable subcomponent: Frontend Login
Vulnerability Type: SQL Injection
Affected Versions: Versions 6.2.0 to 6.2.25 and 7.6.0 to 7.6.9
Severity: Medium
Suggested CVSS v2.0: AV:N/AC:M/Au:S/C:P/I:P/A:N/E:P/RL:O/RC:C
CVE: not assigned yet
Problem Description: Failing to properly escape user input, the frontend login
component is vulnerable to SQL Injection. A valid frontend user account is
needed to exploit this vulnerability.
Solution: Update to TYPO3 versions 6.2.26 or 7.6.10 that fix the problem
described.
Credits: Thanks to Oliver Hader 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.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-017: Information Disclosure in TYPO3 Backend
July 19, 2016
Category: TYPO3 CMS
Author: Nicole Cordes
Keywords: Backend, Information Disclosure
It has been discovered, that TYPO3 is susceptible to Information Disclosure.
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerable subcomponent: Backend
Vulnerability Type: Information Disclosure
Affected Versions: Versions 6.2.0 to 6.2.25, 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0
Severity: Low
Suggested CVSS v2.0: AV:N/AC:M/Au:N/C:P/I:N/A:N/E:P/RL:O/RC:C
CVE: not assigned yet
Problem Description: The TYPO3 backend module stores the username of an
authenticated backend user in its cache files. By guessing the file path to the
cache files it is possible to receive valid backend usernames.
Solution: Update to TYPO3 versions 6.2.26, 7.6.10 or 8.2.1 that fix the problem
described.
Credits: Thanks to Matthias Kappenberg 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.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-018: Cross-Site Scripting vulnerability in typolinks
July 19, 2016
Category: TYPO3 CMS
Author: Nicole Cordes
Keywords: TYPO3 CMS, Cross-Site Scripting, XSS
It has been discovered, that TYPO3 is susceptible to Cross-Site Scripting.
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerability Type: Cross-Site Scripting
Affected Versions: Versions 6.2.0 to 6.2.25, 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0
Severity: Low
Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:N/I:P/A:N/E:F/RL:O/RC:C
CVE: not assigned yet
Problem Description: All link fields within the TYPO3 installation are
vulnerable to Cross-Site Scripting as authorized editors can insert data
commands by using the url scheme "data:".
Solution: Update to TYPO3 versions 6.2.26, 7.6.10 or 8.2.1 that fix the
problem described. The typoLink() function disables the insecure url scheme
"data:".
Credits: Thanks to Valentin Despa 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.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-019: Environment Variable Injection
July 19, 2016
Category: TYPO3 CMS
Author: Helmut Hummel
Keywords: Environment variable injection, guzzle
It has been discovered, that PHP exposes the risk of Environment Variable
Injection and TYPO3 is vulnerable through third party library guzzlehttp/guzzle
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerability Type: Environment Variable Injection
Affected Versions: Versions 8.0.0 to 8.2.0
Severity: Low
related CVE: CVE-2016-5385
Problem Description: PHP, when used as CGI, FPM or HHVM, exposes http headers
also as environment variables starting with "HTTP_". TYPO3 version 8.2.0 is
vulnerable because it uses the third party library guzzlehttp/guzzlel, which
makes use of the environment variable "HTTP_PROXY". Read
https://www.symfony.fi/entry/httpoxy-vulnerability-hits-php-installations-using-fastcgi-and-php-fpm-and-hhvm
or https://httpoxy.org/ for further details.
Solution: Update to TYPO3 version 8.2.1 that fixes the problem described.
General Advice: Follow the recommendations that are given in the TYPO3 Security
Guide. Please subscribe to the typo3-announce mailing list.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------------------------------------------------------------
TYPO3-CORE-SA-2016-020: Cross-Site Scripting in third party library
mso/idna-convert
July 19, 2016
Category: TYPO3 CMS
Author: Helmut Hummel
Keywords: Cross-Site Scripting, mso/idna-convert
It has been discovered, that TYPO3 ships example code of mso/idna-convert
library that is vulnerable to Cross-Site Scripting
Component Type: TYPO3 CMS
Release Date: July 19, 2016
Vulnerability Type: Cross-Site Scripting
Affected Versions: 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0
Severity: Low
Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:N/I:P/A:N/E:F/RL:O/RC:C
CVE: not assigned yet
Problem Description: TYPO3 ships example code from mso/idna-convert library in
the vendor folder, which is vulnerable to Cross-Site Scripting.
Solution: Update to TYPO3 versions 7.6.10 or 8.2.1 that fix the problem
described.
Alternative Solution: Make sure to not expose the vendor directory to the
publicly accessible document root. In composer managed installation, make sure
to configure a dedicated web folder. In general it is recommended to not expose
the complete typo3_src sources folder in the document root.
Credits: Thanks to Frank Huber 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.
General Note: All security related code changes are tagged so that you can
easily look them up on our review system.
- --------------------------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
iQIVAwUBV47/9ox+lLeg9Ub1AQjaCA//cVV7na9IYoFP9VU1ghOOIawrWJDUUEXL
99R05zYK+bmeSuJ17vIXlB3BraWWa2QZxxq42+AHhkzowMRtV7OyfFk2xybBvFYY
1bGi0RUxCBo1YMhGyHPvvBSGNL24GOVn0BN4kSahRCmTS68LtZaMjBwe9DWZNZdb
wMcueFbguXyeJdvYb0Gn6nXMwD8OT9Tzk75o3vheqaOjP1WUWdOvkTunWKeQOaTI
qIQiqtYZtQ5qLfXfip9pEUdzxEijqdtgVaE+bj5HDblZ+4W8+Tx/2q4FxVzq4cNN
oGZRzJqzAiiNSVSSi/0wCl/X6lRGy0Djvc3AWyMrAgpHPpCzaZzvUgLEhdkdFa8h
yxXknwL8ufiWW18CZ5nn0es979sz6soUj7abvxOQLUEs9u1u9QXcWKUu2qZR8Zdo
7ZTh/ETsLV7MR6NaW3CIvZyx0R5ErVuq/CCpipA1eUzklEZDS3GbhfhFrVoYjBV8
0qd2JvTmsOvM+u0p04A1jz01b2gV3OISBpraLwWioDa9VvL7hc9Pui06HH3A+JFR
LI6v9PbH4sDtr4ISdC1WQsfGdMTHDPBXAnWprl2yKVstXQWI5dcIIaVCB9M+d9BM
9sCGfYSOPNB2SDbyAlqwOGg5Ca5CLpS8ryleH3ql163thedE7aELUzcqk98EzJY6
g8JBVFOhwLs=
=i6wt
-----END PGP SIGNATURE-----