Vulnerability Summary
Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9 does not properly handle cases where an HTTP response occurs before finishing the reading of an entire request body, which allows remote attackers to cause a denial of service (memory consumption) via a series of aborted upload attempts.
Details
CVE-2014-0230
Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9 does not properly handle cases where an HTTP response occurs before finishing the reading of an entire request body, which allows remote attackers to cause a denial of service (thread consumption) via a series of aborted upload attempts.
From Apache Tomcat:
“When a response for a request with a request body is returned to the user agent before the request body is fully read, by default Tomcat swallows the remaining request body so that the next request on the connection may be processed. There was no limit to the size of request body that Tomcat would swallow. This permitted a limited Denial of Service as Tomcat would never close the connection and a processing thread would remain allocated to the connection.”
Learn more at Tomcat Apache
Published
Last Update: 3/11/2022
Initial Public Release: 6/17/2015
Advisory ID: PLYGN15-04
CVE ID: CVE-2014-0230
CVSS Score: 7.8
CVSS: 2.0/AV:N/AC:L/Au:N/C:N/I:N/A:C
Product Affected
PRODUCT |
STATUS |
Media Manager – All Versions |
Not Vulnerable |
CMAD (CMA Desktop) – All Versions |
Not Vulnerable |
CX5000 – All Versions |
Not Vulnerable |
Video Border Proxy (VBP) – All Versions |
Investigating |
CX Product Line, All Other Video Versions |
Not Vulnerable |
RealPresence Desktop – All Versions |
Not Vulnerable |
Group Series – All Versions |
Not Vulnerable |
Capture Station – All Versions |
Investigating |
RealPresence Access Director (RPAD) – All Versions |
Investigating |
CloudAXIS MEA – All Versions |
Investigating |
CloudAXIS WSP – All Versions |
Investigating |
Platform Director – All Versions |
Investigating |
HDX – All Versions |
Not Vulnerable |
RealPresence Resource Manager (RPRM) |
Investigating |
RSS 4000 – All Versions |
Investigating |
Distributed Media Application (DMA) – All Versions |
Investigating |
Capture Server |
Investigating |
Content Sharing Suite Client/Server – All Versions |
Investigating |
RealPresence Collaboration Server (RMX) – All Versions |
Investigating |
RealPresence Mobile – All Versions |
Not Vulnerable |
UC Phones – VVX - All Versions |
Not Vulnerable |
UC Phones – SPIP & SSIP – All Versions |
Not Vulnerable |
Solution
There are no specific mitigations at this time for this vulnerability. Security best practices should be followed, and some recommendations can be found in Recommended Security Best Practices for Unified Communications.
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 | 6/17/2015 | Original publication |
2.0 | 3/11/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.