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
Poly RealPresence Resource Manager (RPRM) systems may be vulnerable to remote code injection, which if exploited might allow attackers to execute system commands or gain remote access.
JBoss Application Server is vulnerable to remote command execution via the ‘HTTP Invoker’ service that provides Remote Method Invocation (RMI over HTTP). Access to the URLs ‘/invoker/EJBInvokerServlet’ or ‘/invoker/JMXInvokerServlet’ with detached invoker operation via an HTTP POST request can be used to deploy a malicious remote Web Application Archive.
This exploit is consistent with CVE: 2013-4810 and OSVDB-ID: 97153.
Details
CVE 2013-4810
JBoss Application Server is vulnerable to remote command execution via the ‘HTTP Invoker’ service that provides Remote Method Invocation (RMI over HTTP). Access to the URLs ‘/invoker/EJBInvokerServlet’ or ‘/invoker/JMXInvokerServlet’ with detached invoker operation via an HTTP POST request can be used to deploy a malicious remote Web Application Archive.
Poly released a firmware update to address this vulnerability.
Published
Last Update: 3/4/2022
Initial Public Release: 12/20/2013
Advisory ID: PLYUI13-07
CVE ID: CVE-2013-4810
CVSS Score: 10.0
CVSS:2 /AV:N/AC:L/Au:N/C:C/I:C/A:C
Product Affected
| PRODUCT | FIRMWARE | FIX |
|---|---|---|
| RealPresence Resource Manager | Prior to 7.1.1 HF6 | 8.1 and above |
Solution
At this time, Poly has developed hot fix RPRM 7.1.1 HF6 which removes the vulnerability. This is available through Poly support. Official release 8.1 resolves this issue as well and can be downloaded from support.poly.com These fixes are available through Poly support. Poly recommends customers upgrade to firmware build 8.1 or later.
Workaround
Administrators concerned about this attack vector should patch their RPRM system to the latest available fix as soon as practical. Prior to patching, this potential vulnerability can be mitigated by placing the RPRM system in Maximum Security Mode (MSM) or behind a firewall. Access through ports 80 and 8080 should be blocked. Access should be restricted to secure ports 443 and/or 8443. Any unauthorized POST requests to ‘/invoker/JMXInvokerServlet’ on an RPRM system should be treated as highly suspicious, as should outbound requests for access to files with the extensions ‘.war’ or ‘.pl’.
Poly recommends that customers evaluate network access control lists, firewalls, and other network protections to ensure that they have been deployed in a manner that is consistent with security best practices. The risk presented by this potential vulnerability to Poly products, as well as other networked devices, may be mitigated by these controls. Customers should also ensure that Poly products have been configured as recommended by Poly implementation guides. Customers may wish to implement additional event monitoring and review until such time that an update is installed.
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.
RECOGNITION
Poly would like to thank Steven Bairstow from Security Operations & Services (SOS), The Pennsylvania State University for reporting security vulnerabilities to us and for their coordinated disclosure.
Revision History
| VERSION | DATE | DESCRIPTION |
|---|---|---|
| 1.0 | 12/12/2013 |
Initial Release |
| 2.0 | 3/4/2022 |
Format Changes |
©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.