Microsoft Vulnerability Research Advisory MSVR12-009
Vulnerability in LongTail Video JW Player Could Allow Cross-Site Scripting
Published: June 19, 2012
Microsoft is providing notification of the discovery and remediation of a vulnerability affecting LongTail Video JW Player software version 5.9.2145 and earlier versions. Microsoft discovered and disclosed the vulnerability under coordinated vulnerability disclosure to the affected vendor, LongTail Video. LongTail Video has remediated the vulnerability in their software.
A vulnerability exists in the way that the JW Player handles user input that results in a cross-site scripting issue. An attacker who successfully exploited the vulnerability could perform cross-site scripting attacks against users that visit websites that utilize JW Player. An attacker could then potentially run script in the context of the site user.
Microsoft Vulnerability Research reported this issue to and coordinated with LongTail Video to ensure remediation of this issue. The vulnerability has been assigned the entry, CVE-2012-3351, in the Common Vulnerabilities and Exposures list. For more information, including information about updates from LongTail Video, see LongTail Video Ticket 1585.
- An attacker must convince a victim to click a malicious link that has a specially crafted URL.
Purpose and Recommendation
Purpose of Advisory: To notify users of a vulnerability and its remediation.
Advisory Status: Advisory published.
Recommendation: Review the Suggested Actions section and configure as appropriate.
For more information about this issue, see the following references:
|Common Vulnerabilities and Exposures||CVE-2012-3351|
Affected and Non-Affected Software
This advisory discusses the following software:
|LongTail Video JW Player version 5.9.2145 and earlier versions|
|LongTail Video JW Player version 5.9.2206|
Frequently Asked Questions
What is the scope of this advisory?
This advisory is part of a coordinated release with affected vendors to inform customers of a security issue that may affect their systems.
Is this a security vulnerability that requires Microsoft to issue a security update?
No. This vulnerability has been fixed via an update from the affected third-party vendors. The update remediates the software listed in the table, Affected Software.
What is the scope of the vulnerability?
This is a cross site scripting vulnerability. An attacker who successfully exploited the vulnerability could perform cross-site scripting attacks against users that visit websites that utilize JW Player. An attacker could then potentially run script in the context of the site user.
What causes the vulnerability?
The vulnerability is caused when JW Player performs incomplete sanitization of input provided by the user.
What might an attacker use this vulnerability to do?
An attacker could leverage this issue to serve a malicious flash file in the context of a trusted site. An attacker could perform cross-site scripting attacks against users that visit websites that utilize JW Player. An attacker could then potentially run script in the context of the site user.
How could an attacker exploit the vulnerability?
An attacker could exploit this issue by convincing a user to click a specially crafted link.
Update to the latest version of JW Player.
Microsoft thanks the following:
- Ali Pezesch and Jiri Richter of Microsoft and LongTail Video for working toward a resolution
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
- V1.0 (June 19, 2012): Advisory published.
Built at 2014-04-18T13:49:36Z-07:00