solution Contentsolution Content

HDX - IMPROPER NEUTRALIZATION OF INPUT DURING WEB PAGE GENERATION & CROSS-SITE REQUEST FORGERY

Poly HDX video endpoints (all models) are subject to multiple cross-site Scripting (XSS) vulnerabilities that could be maliciously abused to gain unauthenticated access to the camera or execute JavaScript in the context of pages viewed by administrators.

Severity

High

Advisory ID

PLYTV16-05

Initial public release

6/29/2016

Last update

3/11/2022

Category

Poly

Summary

The web interface of HDX endpoints is subject to persistent unauthenticated cross-site scripting using a crafted username with an incoming call, which may allow malicious users to access or control the camera.

A malicious user with administrative privileges can submit diagnostic content that contains embedded JavaScript. Stored XSS occurs when a web application gathers input from a user, and then stores that input for others to potentially retrieve and view. Any administrator who subsequently views the malicious submission will execute the JavaScript in the context of their web browser.

Relevant Common Vulnerabilities and Exposures (CVE) List

Poly would like to thank an Anonymous Security Researcher of Beyond Security’s SecuriTeam Secure Disclosure for reporting the persistent unauthenticated XSS vulnerability to us and for their coordinated disclosure.

Poly would like to thank Vincent Hutsebaut of NCIRC for reporting the stored XSS vulnerabilities to us and for their coordinated disclosure.

Learn more about CVSS 3.0 base metrics, which range from 0 to 10.

Resolution

Poly recommends customers upgrade to firmware build 3.1.10 or later.

For customers who cannot immediately upgrade to a non-vulnerable HDX system software version, the most effect means to mitigate these vulnerabilities is to limit access to the web interface of the HDX to only trusted users, and to limit sources of incoming calls to trusted remote endpoints.

The vulnerable field for the stored XSS is only accessible to HDX administrators via the web. This vulnerability is not triggered through the HDX console, only through the web interface. In addition, we recommend administrators follow standard best practices and change all default passwords and restrict network web access to the HDX unit using firewalls and whitelists.

Affected products

Identify the affected products for this issue.

List of products

Product

Firmware

Fix

HDX 4000

Prior to 3.1.9

3.1.10 and above

HDX 6000

Prior to 3.1.9

3.1.10 and above

HDX 7000

Prior to 3.1.9

3.1.10 and above

HDX 8000

Prior to 3.1.9

3.1.10 and above

HDX 9000

Prior to 3.1.9

3.1.10 and above

Revision history

This document has been revised according to the following information.

List of versions

Version

Description

Date

3.0

Format Changes

3/11/2022

2.0

Additional Details / Acknowledgement

9/16/2016

1.0

First Announcement

6/29/2016

Additional information

Follow these links for additional information.

Third-party security patches

Third-party security patches that are to be installed on systems running Poly software products should be applied in accordance with the customer's patch management policy.

Contact

Any customer using an affected system who is concerned about this vulnerability within their deployment should contact Poly Technical Support(888) 248-4143, (916) 928-7561, or visit the Poly Support Site.

Security bulletin archive

To view released Security Bulletins, visit https://support.hp.com/security-bulletins.

It is strongly recommended that security related information being communicated to HP be encrypted using PGP, especially exploit information.

Download HP’s security-alert PGP key

Legal information

©2022 Plantronics, Inc. All rights reserved.

TrademarksPoly, the propeller design, and the Poly logo are trademarks of Plantronics, Inc. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Poly.

DisclaimerWhile Poly uses reasonable efforts to include accurate and up-to-date information in this document, Poly makes no warranties or representations as to its accuracy. Poly assumes no liability or responsibility for any typographical errors, out of date information, or any errors or omissions in the content of this document. Poly reserves the right to change or update this document at any time. Individuals are solely responsible for verifying that they have and are using the most recent Technical Bulletin.

Limitation of LiabilityPoly and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Poly and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Poly has been advised of the possibility of such damages.