Multiple vulnerabilities discovered in RealPresence Resource Manager version 8.3.2. Of the nine vulnerabilities identified, seven have been fixed in RPRM 8.4. Two remaining vulnerabilities are exploitable only by users with administrator or auditor roles, and Poly will be issuing an update to address these vulnerabilities in the near future.
Poly RealPresence Resource Manager 8.3.2 and earlier contains instances of weak passwords.
An absolute path disclosure vulnerability in Poly RealPresence Resource Manager 8.3.2 and earlier allows an attacker to see the path to the web root. This information leakage can be used to refine attacks against the webserver.
Poly RealPresence Resource Manager 8.3.2 and earlier transmits session-IDs as a URL parameter, which can be used by an unprivileged attacker to gain admin-level privileges.
Poly RealPresence Resource Manager 8.3.2 and earlier allow remote authenticated administrator users to read or write arbitrary files.
Poly RealPresence Resource Manager 8.3.2 and earlier contains a sudo misconfiguration that could allow an attacker to escalate their privileges.
Plaintext passwords stored in logfiles
RPRM generates log data which includes plaintext passwords. This weakness in combination with the previous vulnerability allows an unprivileged attacker to escalate his privileges to the admin level in the web interface. The “previous vulnerability” mentioned by SEC Consult has been fixed in RPRM 8.4. Only users with administrator or auditor role can read the affected logs. Poly is working on the issue and will soon release an update to address this.
The separation of users relies on the fact that conference IDs are not guessable, but as soon as an information disclosure vulnerability allows an attacker to gather conference IDs authorization can be bypassed. The arbitrary file download vulnerability (2) allows an attacker to collect valid conference IDs. The “arbitrary file download vulnerability” mentioned by SEC Consult has been fixed in RPRM 8.4. Only users with an administrator or auditor role can read logfiles that contain valid conference IDs. Poly is working on the issue and will soon release an update to address this.
Last Update: 3/11/2022
Initial Public Release: 6/26/2015
Advisory ID: PLYUC15-09
CVE ID: CVE-2015-4681
CVSS Score: 7.8
CVE ID: CVE-2015-4682
CVSS Score: 6.5
CVE ID: CVE-2015-4683
CVSS Score: 9.8
CVE ID: CVE-2015-4684
CVSS Score: 6.5
CVE ID: CVE-2015-4685
CVSS Score: 7.0
|Poly RealPresence Resource Manager (RPRM)||
RPRM Software 8.3.2 and prior
|RPRM Software 8.4 or later|
Poly recommends customers upgrade to app version 8.4 or later.
There is no workaround.
Poly would like to thank Rene Freingruber from SEC Consult Vulnerability Lab for reporting security vulnerabilities to us and for their coordinated disclosure.
|2.0||3/9/2022||Format changes and Detail clarifications|
©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.