asb99-02.coldfusion_example_apps
6dc85f5e6735909fad69b69c3d1e23a59edc883a5135260c057dce50792ec6ee
Allaire Security Bulletin (ASB99-02)
ColdFusion Example Applications and Sample Code Exposes Servers
Originally Posted: February 4, 1999
Last Update: May 19, 1999
Summary
ColdFusion Server 4.0 includes some example applications and sample
code that expose security issues. Allaire recommends that customers
install the [4]ColdFusion 4.0.1 Update, available for download from
the Allaire site since April 29, 1999, which resolves the issues in
ColdFusion 4.0. In addition, the example applications included with
ColdFusion 2.x and 3.x also expose potential security vulnerabilities.
These issues are not addressed by the 4.0.1 Update, and the 2.x or 3.x
example applications should be removed or secured. In general, Allaire
recommends that customers avoid installing documentation and sample
applications (CFDOCS directory) on production machines, and restrict
access to the CFDOCS directory where it is installed on workstations.
Issue
ColdFusion Server 4.0 ships with several example applications and more
than 200 sample code files. These files are installed with
documentation under the CFDOCS directory. There are basically three
sets of security issues that have been identified with the example
applications and sample code.
First, one of the features of the example applications is a page that
displays the source code of the examples in a browser. This page
exposes the ability to view source code in other files on the server.
Second, the sample code, sometimes referred to as "runnable code
snippets," that are included as references in the electronic version
of the CFML Language Reference expose a number of security issues
including the ability to view files and directory information, make
http calls from a machine, and launch denial-of-service attacks.
Third, the Syntax Checker, which is provided to verify that existing
CFML code will run on version 4.0, can be used remotely to initiate a
denial-of-service attack by fully occupying the ColdFusion service
with unnecessary file processing.
ColdFusion Server 2.x and 3.x shipped with several example
applications that have been identified as potential security problems.
(Note: Because these applications are not automatically removed by the
4.x installation, they may pose a threat to customers who upgraded
from the 2.x and 3.x releases to version 4.0 or 4.0.1 of ColdFusion
Server.) The risks exposed include the ability to spoof the local host
IP (127.0.0.1) thereby circumventing security that restricts access
based on local host IP, the ability upload executable files (using the
spoofed IP address), and the ability to set up mailing lists with a
mailing list example application.
Affected Software Versions
* ColdFusion Server 2.x, 3.x, 4.0 (all editions)
What Allaire is Doing
Allaire has addressed the ColdFusion 4.0 issues in the [5]ColdFusion
4.0.1 maintenance release, available for download from the Allaire
site since April 29, 1999.
[6]Download - ColdFusion 4.0.1 maintenance release
In general, Allaire is recommending that customers remove all example
applications and documentation (the entire CFDOCS directory) from
production servers and restrict access to CFDOCS on developer
workstations.
What Customers Should Do
Customers who are only running ColdFusion 4.0 should install the
[7]ColdFusion 4.0.1 maintenance release on all of their installations
of ColdFusion Server 4.0. Customers running other versions of
ColdFusion or customers who have upgraded to 4.0 or 4.0.1 should
completely remove the CFDOCS directory on production servers and
restrict access to it on developer workstations.
Furthermore, we recommend that customers remove all documentation,
sample code, example applications, and tutorials from production
servers. The examples that are installed with ColdFusion are installed
in the CFDOCS directory, which is normally installed in the root of
the Web server directory. This directory should not be installed on
production servers and access to the CFDOCS directory should be
restricted on developer workstations. As a general security best
practice, sample code and example applications should not be installed
on production servers.
Revisions
February 4, 1999 Bulletin first released.
April 30, 1999 Bulletin updated to include notice of 4.0.1 fix.
May 19, 1999 Bulletin updated to include 2.x and 3.x issues.
Reporting Security Issues
Allaire is committed to addressing security issues and providing
customers with the information on how they can protect themselves. If
you identify what you believe may be a security issue with an Allaire
product, please send an email to secure@allaire.com. We will work to
appropriately address and communicate the issue.
Receiving Security Bulletins
When Allaire becomes aware of a security issue that we believe
significantly affects our products or customers, we will notify
customers when appropriate. Typically this notification will be in the
form of a security bulletin explaining the issue and the response.
Allaire customers who would like to receive notification of new
security bulletins when they are released can sign up for our security
notification service.
For additional information on security issues at Allaire, please visit
the Security Zone at:
[8]http://www.allaire.com/security
THE INFORMATION PROVIDED BY ALLAIRE IN THIS BULLETIN IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. ALLAIRE DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ALLAIRE
CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER
INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF
BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF ALLAIRE CORPORATION OR
ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY
NOT APPLY.
< a l l a i r e >
Copyright © 1995-99 Allaire Corp., All rights reserved.
[9]Site problems? [10]Service questions? [11]Privacy Policy
References
1. LYNXIMGMAP:http://www1.allaire.com/handlers/index.cfm?ID=8739&Method=Full#allaireHome
2. LYNXIMGMAP:http://www1.allaire.com/handlers/index.cfm?ID=8739&Method=Full#tools
3. javascript:history.back()
4. http://www1.allaire.com/handlers/index.cfm?ID=10712&Method=Full
5. http://www1.allaire.com/handlers/index.cfm?ID=10712&Method=Full
6. http://www1.allaire.com/handlers/index.cfm?ID=10712&Method=Full
7. http://www1.allaire.com/handlers/index.cfm?ID=10712&Method=Full
8. http://www.allaire.com/security
9. mailto:webmaster@allaire.com
10. mailto:info@allaire.com
11. http://www.allaire.com/privacy/