Quick answers
- Is CVE-2016-4056 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-4056 being exploited in the wild.
- How severe is CVE-2016-4056?
- Medium severity, with a CVSS score of 6.1, published 23 January 2017.
- Which products and versions are affected?
- typo3/cms (Packagist) ECOSYSTEM:introduced=6.2.0,fixed=6.2.19.
- Is there a fix for CVE-2016-4056?
- Yes. typo3/cms (Packagist): upgrade to 6.2.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-4056 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2016-4056?
- Check whether you run typo3/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- typo3/cms (Packagist): upgrade to 6.2.19 or later
composer require typo3/cms:^6.2.19
Technical details
A stored cross-site scripting (XSS) vulnerability exists in the Backend component of TYPO3 CMS versions 6.2.0 through 6.2.18. The root cause is a failure to properly encode incoming data within the bookmark toolbar subcomponent. Specifically, an attacker can manipulate the 'module' parameter during a POST request when creating a bookmark to inject a malicious payload. While the attack requires user interaction (viewing the bookmark), it can be triggered by remote attackers to execute arbitrary JavaScript in the context of a logged-in user's session. The issue is resolved in TYPO3 version 6.2.19.
Affected products
- TYPO3 TYPO3 CMS 6.2.0 to 6.2.18
Identifiers
- CVE-2016-4056
- GHSA-ffcm-vhcw-p32r
Timeline
- 2016-02-15: disclosed: Bug reported to TYPO3 team
- 2016-02-23: patched: TYPO3 version 6.2.19 released
- 2016-02-24: advisory: Public disclosure by Integrity Labs
- 2017-01-23: advisory: NVD publication date