Microsoft Content Management Server flaws allow system compromise
Risk
High
Date Discovered
07-12-2002
Description
Three vulnerabilities have been identified in Microsoft Content Management Server (MCMS). The effects of exploitation range from a denial-of-service attack to gaining root access.
Microsoft Content Management Server enables companies to quickly and efficiently build, deploy, and maintain Web sites. Using MCMS, companies can create, publish, and manage Web content, as well as manage the server resources that are available to the site.
The first vulnerability is a buffer overflow that exists in a function that performs user authentication. At least one Web page that is included with MCMS 2001 passes inputs directly to this function that could provide a way for an attacker to overrun the buffer. Exploitation of the vulnerability causes MCMS to fail, resulting in a denial of service. Additionally, code may be run in the context of the MCMS service, which runs as Local System. The potential risk is significantly reduced if the URLScan tool is deployed on the server. In this case, that the vulnerability might only be used for denial-of-service attacks.
Another vulnerability results from the convergence of two flaws that affect a function used to upload files to the server. The first flaw is improper request authentication. Any user can submit an upload request. The second flaw is that it is possible to override the upload location. The function should upload files to a folder that only privileged users can access; it can, however, be overridden to upload files to a temporary folder that allows access by unprivileged users. By exploiting the two flaws in tandem, an attacker could upload an .asp or other file to the server in a location from which it could be executed. Although the attacker does not gain administrative privileges, the attacker's code would execute in the security context of the Web Application Manager, which has similar privileges to those of an interactively logged-on user.
The third vulnerability is in a function that services requests for image files and other resources. Exploitation of this vulnerability could enable an attacker to run SQL commands on the server, which would not only allow data in the MCMS database to be added, changed, or deleted, but would enable the attacker to run operating system commands on the server. Exploitation of this SQL injection vulnerability does not grant the attacker administrative privileges on the server. Instead, any operating system commands would be levied in the security context of the SQL Server 2000 service, which has only Domain User privileges by default.
Platforms Affected
Windows
Components Affected
Microsoft Content Management Server 2001
Recommendations
Patch: Microsoft Content Management Server Patch Q326075
Upgrade your system with this Patch for Unchecked Buffer in Content Management Server Could Enable Server Compromise (Q326075).
References
Source: CVE CAN-2002-0700
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0700
Source: Microsoft MS02-041
URL: http://microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS02-041.asp
Source: CIAC M-107
URL: http://ciac.llnl.gov/ciac/bulletins/m-107.shtml
Source: securityfocus Microsoft Content Management Server 2001 User Authentication Buffer Overflow Vulnerability
URL: http://online.securityfocus.com/bid/5420
Source: securityfocus Microsoft Content Management Server 2001 Arbitrary Upload Location Vulnerability
URL: http://online.securityfocus.com/bid/5421
Source: securityfocus Microsoft Content Management Server 2001 SQL Injection Vulnerability
URL: http://online.securityfocus.com/bid/5422
Copyright (c) 2009 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 Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.
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, Symantec Security Response, and secure@symantec.com 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.
|