Microsoft Content Management Server Remote Code Execution Vulnerability



Date Discovered

April 10, 2007


Microsoft Content Management Server (MCMS) is prone to an arbitrary code-execution vulnerability because the software fails to properly validate user-supplied input. Exploiting this issue allows remote attackers to execute arbitrary machine code on affected computers with the privileges of the vulnerable application.

Technologies Affected

  • HP Storage Management Appliance 2.1
  • Microsoft Content Management Server 2001
  • Microsoft Content Management Server 2001 SP1
  • Microsoft Content Management Server 2002
  • Microsoft Content Management Server 2002 SP1
  • Microsoft Content Management Server 2002 SP2


Block external access at the network boundary, unless external parties require service.
Allow only trusted computers and networks to connect to computers running the affected software. This will limit the potential for remote attackers to exploit this issue.

Run all software as a nonprivileged user with minimal access rights.
Execute all software as a user with minimal privileges. Use additional precautions such as restrictive environments to insulate software that may potentially handle malicious content.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploitation attempts or activity that results from successful exploitation.

Implement multiple redundant layers of security.
As an added precaution, deploy memory-protection schemes (such as non-executable stack/heap configuration and randomly mapped memory segments). This may complicate exploits of memory-corruption vulnerabilities.

Microsoft has released an advisory along with fixes to address this issue in supported versions of affected applications. HP Storage Management Appliance is affected by the issue; please see the referenced HP advisory.



This issue was disclosed in the referenced vendor advisory.

© 1995- Symantec Corporation

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


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 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.