Microsoft IIS File Change Notification Local Privilege Escalation Vulnerability



Date Discovered

February 12, 2008


Microsoft Internet Information Service (IIS) is prone to a local privilege-escalation vulnerability that occurs when handling file change notifications. A local attacker can exploit this issue to execute arbitrary code with SYSTEM-level privileges. Successfully exploiting this issue will result in the complete compromise of affected computers.

Technologies Affected

  • Avaya Messaging Application Server
  • Avaya Messaging Application Server MM 1.1
  • Avaya Messaging Application Server MM 2.0
  • Avaya Messaging Application Server MM 3.0
  • Avaya Messaging Application Server MM 3.1
  • HP Storage Management Appliance 2.1
  • Microsoft IIS 5.0
  • Microsoft IIS 5.1
  • Microsoft IIS 6.0
  • Microsoft IIS 7.0
  • Nortel Networks Centrex IP Client Manager 10.0
  • Nortel Networks Centrex IP Client Manager 9.0


Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
To reduce the likelihood of attacks, allow access to trusted individuals only and implement restricted environments and privileges.

Disable any unneccessary default services.
Disable the FTP root and NNTP root services. This will prevent attackers from uploading malicious files into the FTP root and NNTP root folders.

Modify default ACL settings.
Ensure that the WWW folder does not allow write access to accounts that can execute user-controlled ASP pages.

Microsoft has released patches and an advisory to address this issue. Please see the references for more information.



The vendor reported this issue.

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