Wicket jQuery UI up to 6.28.0/0.9.1/8.0.0-M8 WYSIWYG Editor cross site scripting

Summaryinfo

A vulnerability was found in Wicket jQuery UI up to 6.28.0/0.9.1/8.0.0-M8. It has been declared as problematic. Impacted is an unknown function of the component WYSIWYG Editor. The manipulation results in cross site scripting. This vulnerability is reported as CVE-2017-15719. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as problematic has been found in Wicket jQuery UI up to 6.28.0/0.9.1/8.0.0-M8 (JavaScript Library). Affected is some unknown processing of the component WYSIWYG Editor. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:

In Wicket jQuery UI 6.28.0 and earlier, 7.9.1 and earlier, and 8.0.0-M8 and earlier, a security issue has been discovered in the WYSIWYG editor that allows an attacker to submit arbitrary JS code to WYSIWYG editor.

The bug was discovered 02/25/2018. The weakness was disclosed 03/12/2018 (Website). The advisory is shared for download at openmeetings.apache.org. This vulnerability is traded as CVE-2017-15719 since 10/21/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.

The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• JavaScript Library

Vendor

• Wicket

Name

• jQuery UI

Version

• 0.9.0
• 0.9.1
• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9
• 6.10
• 6.11
• 6.12
• 6.13
• 6.14
• 6.15
• 6.16
• 6.17
• 6.18
• 6.19
• 6.20
• 6.21
• 6.22
• 6.23
• 6.24
• 6.25
• 6.26
• 6.27
• 6.28.0
• 8.0.0-M8

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion