A stored cross site scripting (XSS) vulnerability has been discovered in the web application functionality of Polycom’s QDX 6000 endpoint. This vulnerability could allow a remote attacker to execute arbitrary Javascript on QDX client users’ web browsers.
High
PLYTV18-02
3/2/2018
3/14/2022
Poly
In addition, a cross site request forgery (CSRF) vulnerability has been discovered in QDX’s web application interface. If a user who is currently logged into the QDX were to point their browser to an attacker-controlled website that contains the CSRF attack, this vulnerability could allow the attacker to change arbitrary configuration settings on the QDX.
CVE 2018-7564 – QDX 6000 Stored XSS
Stored XSS exists on Poly QDX 6000 devices.
CVE 2018-7565 – QDX 6000 CSRF
CSRF exists on Poly QDX 6000 devices.
Poly released a firmware update to address this vulnerability. There is no workaround.
Poly would like to thank Bhaskar Borman from @BhaskarBorman on Twitter for reporting security vulnerabilities to us and for their coordinated disclosure.
CVE ID |
CVS 3.0 |
Severity |
Vector |
---|---|---|---|
CVE-2018-7564 |
6.1 |
Medium |
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
CVE- 2018-7565 |
8.8 |
High |
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Learn more about CVSS 3.0 base metrics, which range from 0 to 10.
QDX 6000 is no longer supported by Poly, and no code updates are planned for fixing these vulnerabilities. Instead, Poly recommends applying the mitigations listed below or updating to a supported product such as Poly Group Series endpoints.
Poly recommends following standard best practices for Unified Communications, as detailed in our best practices paper.
In addition, Poly recommends:
Enabling security mode: This can be done by going to the QDX web UI > admin settings > general settings > check the box for “security mode”, and then clicking on the “update” button.
Disabling web remote access: This can be done by going to the QDX web UI > admin settings > general settings > uncheck the box for “Web” under “Enable Remote Access”, and then clicking the “update” button.
Identify the affected products for this issue.
Product |
Firmware |
Fix |
---|---|---|
QDX 6000 |
4.0.2 and prior |
End of Support |
This document has been revised according to the following information.
Version |
Description |
Date |
---|---|---|
2.0 |
Format Changes |
3/14/2022 |
1.0 |
Initial Release |
3/2/2018 |
Follow these links for additional information.
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.
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.
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.
©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.