Macromedia JRun IIS ISAPI Filter GET Request Buffer Overrun Vulnerability



Date Discovered

November 7, 2002


The Macromedia JRun IIS ISAPI handler is prone to a remotely exploitable buffer overrun condition. The issue is due to a lack of bounds checking on requested filenames. It is possible to trigger the overrun if a filename of excessive length is requested. This vulnerability has been reported to affect Microsoft Windows operating systems. Other platforms may not be affected by this issue.

Technologies Affected

  • Macromedia ColdFusion Server MX 6.0.0
  • Macromedia JRun 3.0.0
  • Macromedia JRun 3.1.0
  • Macromedia JRun 4.0.0


Block external access at the network boundary, unless external parties require service.
If appropriate, block external access to the server at the network boundary. Filter untrusted or malicious network traffic at border routers and network firewalls.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy network intrusion detection systems (NIDS). Audit NIDS and webserver logs for signs of malicious network activity.

Run all software as a nonprivileged user with minimal access rights.
Running the server with the least privileges required will reduce the consequences of successful exploitation.

Implement multiple redundant layers of security.
Deploy network intrusion detection systems (NIDS). Audit NIDS and webserver logs for signs of malicious network activity.

Macromedia has released an updater for customers using affected ColdFusion MX releases. Additionally, Macromedia has released patches to address this issue.



Discovered by Riley Hassell of eEye Digital Security.

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