solution Contentsolution Content

VVX 410 / VVX 411 - MULTIPLE VULNERABILITIES

Multiple vulnerabilities were discovered in VVX 410 (fw: 5.9.4.3247) and VVX 411 (fw: 6.2.0.3937) utilizing Better Together over Ethernet (BToE) application 4.4.0.

Severity

Medium

Advisory ID

PLYVC20-05

Initial public release

6/27/2023

Last update

6/27/2023

Category

Poly

Details

CVE 2020-12871

Poly VVX 410 and 411 allow unauthenticated access to the BToE service via the SSH protocol.

CVE 2020-13635

A vulnerability in the Poly VVX 410 and 411 allows an unlimited number of failed authentication pairing code attempts.

CVE 2020-13636

The Poly VVX 411 is vulnerable to Authentication Bypass in Automatic Pairing Mode

Relevant Common Vulnerabilities and Exposures (CVE) List

Poly would like to thank the Competence Center for IT-Security from FZI Research Center for Information Technology for reporting security vulnerabilities to us and for their coordinated disclosure.

List of CVE IDs

CVE ID

CVS 3.0

Severity

Vector

CVE-2020-12871

6.5

Medium

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L

CVE-2020-13635

6.5

Medium

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L

CVE-2020-13636

6.5

Medium

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L

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

PSR-2020-0025

Resolution

Poly recommends customers utilizing BToE with the identified VVX phones upgrade to the respective firmware build or later.

There is no workaround.

Affected products

Identify the affected products for this issue.

List of products

Products

Firmware

Fix

VVX 101, VVX 150, VVX 201, VVX 250, VVX 301, VVX 311, VVX 350, VVX 401, VVX 411, VVX 450, VVX 501, VVX 601

Prior to UC Software 6.3.1 AE

Poly UC Software 6.3.1 AE (split)

Revision history

This document has been revised according to the following information.

List of versions

Version

Description

Date

1.0

Initial Release

6/27/2023

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.