A vulnerability in the web-based management interface of Obihai OBi1022 phones running EX version firmware, up to 5.1.11 on Build: 4858EX.1311, if exploited, could allow an authenticated, remote attacker with admin privileges to execute arbitrary code or cause a denial of service (DoS) condition.
On the Polycom Obihai Obi1022 VoIP phone with firmware 5.1.11, a command injection (missing input validation) issue in the NTP server IP address field for the "Time Service Settings web" interface allows an authenticated remote attacker in the same network to trigger OS commands via shell commands in a POST request.
Poly released a firmware update to address this vulnerability. There is no workaround.
Last Update: 3/7/2022
Initial Public Release: 8/7/2019
Advisory ID: PLYVC19-07
CVE ID: CVE-2019-14259
CVSS Score: 8.0
Prior to 5.1.11
|Update to 5.1.11 (Build: 4983EX)|
Poly recommends customers upgrade to firmware build 5.1.11 or later.
Download OBi Phone Firmware update.
In addition, as a further mitigation and aligned with standard security best practices, Poly also recommends that customers change the Admin password on the phones from a default or weak password to a strong (minimum 10 character) password. This mitigation limits the ability of the attacker to compromise the phone and is the quickest measure that can be taken to reduce risk.
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.
Poly would like to thank Stephan Huber and Philipp Roskosch from Fraunhofer SIT for reporting security vulnerabilities to us and for their coordinated disclosure.
©2022 Plantronics, Inc. All rights reserved.
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.
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.