Perforce P4Web Denial Of Service through resource

2007.12.21
Credit: Oliver Karow
Risk: Medium
Local: No
Remote: Yes
CWE: CWE-399


CVSS Base Score: 7.8/10
Impact Subscore: 6.9/10
Exploitability Subscore: 10/10
Exploit range: Remote
Attack complexity: Low
Authentication: No required
Confidentiality impact: None
Integrity impact: None
Availability impact: Complete

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Symantec Vulnerability Research http://www.symantec.com/research Security Advisory Advisory ID: SYMSA-2007-015 Advisory Title: Perforce P4Web Denial Of Service through resource starvation Author: Oliver Karow / Oliver_Karow (at) symantec (dot) com [email concealed] Release Date: 19 DEC 2007 Application: Perforce 2006.1 Platform: Win32 Severity: Remotely exploitable - Denial Of Service Vendor status: Resolved CVE Number: CVE-2007-6349 Reference: http://www.securityfocus.com/bid/26806 Overview: - From wikipedia: "Perforce is a commercial Revision Control (RC) system. It is developed by Perforce Software, Inc. and was founded in 1995 by Christopher Seiwald. The Perforce system is based on a client/server model with the server managing the collection of source versions in one or more depots. The server software runs on the Unix, Mac OS X, or Microsoft Windows operating systems. The client provides graphical and command line tools for a large number of operating systems. Also available is a suite of plugins that integrate with various programming IDEs and third party applications, such as XCode, Autodesk 3D Studio Max, Alias Maya, Adobe Photoshop, Microsoft Office, Eclipse and Emacs. Other features of the system include support for reporting (i.e. notifying users when a file has changed), branching and merging, and defect tracking." There is a denial of service (DoS) vulnerability in the P4Web Daemon which make it possible to enforce a full CPU usage of the system, by sending a single, special crafted HTTP request. Details: A single HTTP request with the Content-Length header variable set to a value greater than zero in a request which no body, will cause the P4Webs.exe process to consume 99% of CPU time on the target system. of up to 99%. The attack can be executed remotely. No authentication is required for exploitation. Vendor Response: Perforce has confirmed an issue with Windows-based operating systems and P4Web versions 2006.2 and prior that can result in the P4Web host machine becoming unusable due to excessive CPU usage. This was discovered by our QA department in February of 2007, and addressed in our 2007.2 release. Recommendation: Users concerned about this issue should upgrade to P4Web 2007.2 or later, available at no charge from: ftp://ftp.perforce.com/perforce/r07.2/bin.ntx86/p4webinst.exe Common Vulnerabilities and Exposures (CVE) Information: The Common Vulnerabilities and Exposures (CVE) project has assigned the following names to these issues. These are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. CVE-2007-6349 - -------Symantec Consulting Services Advisory Information------- For questions about this advisory, or to report an error: cs_advisories (at) symantec (dot) com [email concealed] For details on Symantec's Vulnerability Reporting Policy: http://www.symantec.com/research/Symantec-Responsible-Disclosure.pdf Consulting Services Advisory Archive: http://www.symantec.com/research/ Consulting Services Advisory PGP Key: http://www.symantec.com/research/Symantec_Consulting_Services_Advisories _PGP.asc - -------------Symantec Product Advisory Information------------- To Report a Security Vulnerability in a Symantec Product: secure (at) symantec (dot) com [email concealed] For general information on Symantec's Product Vulnerability reporting and response: http://www.symantec.com/security/ Symantec Product Advisory Archive: http://www.symantec.com/avcenter/security/SymantecAdvisories.html Symantec Product Advisory PGP Key: http://www.symantec.com/security/Symantec-Vulnerability-Management-Key.a sc - --------------------------------------------------------------- Copyright (c) 2007 by Symantec Corp. Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Consulting Services. Reprinting the whole or part of this alert in any medium other than electronically requires permission from cs_advisories (at) symantec (dot) com. [email concealed] Disclaimer The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information. Symantec, Symantec products, and Symantec Consulting Services are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHaCx/uk7IIFI45IARAgT0AKCeOqwe0X+otU9ipBRsyZrloXRwnQCeO81L KnCl3WqUuM9HdIvyfI77crs= =Jrog -----END PGP SIGNATURE-----


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top