As of August 29, 2022, HP Inc. completed the acquisition of Poly. For HP product support, please visit the HP Customer Support site.
Vulnerability Summary
Multiple vulnerabilities discovered in the firmware build 2.2.1.1 of the EagleEye Director II. The versions of Python, OpenSSL, and Apache contain multiple vulnerabilities or are no longer supported. The version of TLS and use of certain cipher suites contain vulnerabilities.
Published
Last Update: 3/7/2022
Initial Public Release: 3/7/2022
Advisory ID: PLYPL21-11
Details
Apache Version
Multiple vulnerabilities exist within the version of Apache, see the links below for detailed information.
- https://httpd.apache.org/security/vulnerabilities_24.html#2.4.33
- https://httpd.apache.org/security/vulnerabilities_24.html#2.4.34
- https://httpd.apache.org/security/vulnerabilities_24.html#2.4.35
- https://httpd.apache.org/security/vulnerabilities_24.html#2.4.38
- https://downloads.apache.org/httpd/CHANGES_2.4
Python Version
The version of Python contains multiple vulnerabilities, see the links below for detailed information.
TLS Version 1.0 Protocol Detection
The remote service accepts TLS 1.0, which contains multiple vulnerabilities, see the link below for detailed information.
OpenSSL Version
Multiple vulnerailities exist within the installed version of OpenSSL, see the links below for detailed information.
- https://www.openssl.org/news/secadv/20210824.txt
- https://www.openssl.org/policies/releasestrat.html
- https://www.openssl.org/news/secadv/20171102.txt
SSL Medium Strength Cipher Suites Supported (SWEET32)
The remote service supports medium strength SSL ciphers, which is vulnerable to SWEET32, see the link below for detailed information.
Product Affected
| PRODUCTS | FIRMWARE | FIX |
|---|---|---|
| EEDII | 2.2.1.1 |
2.2.2.1 |
Solution
Poly recommends all customers upgrade to the latest version. Update EaglelEye Director II to firmware version 2.2.2.1 or later. This version contains patches for Python, Apache, and OpenSSL. This fix version removes the use of weak ciphers and TLS 1.0.
Workaround
There is no workaround.
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.
Revision History
| VERSION | DATE | DESCRIPTION |
|---|---|---|
| 1.0 | 03/07/2022 | Initial Release |
©2022 Plantronics, Inc. All rights reserved.
Trademarks
Poly, 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.
Disclaimer
While 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 Liability
Poly 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.