ColdFusion 11 Update 13

ColdFusion 11 Update 13 (release date September 12, 2017) includes the following changes:

• Bug fixes, language updates, and other updates
• Vulnerability fixes, mentioned in the security bulletin APSB17-30.

This update is cumulative and includes fixes from all the previous ColdFusion 11 updates.

To see a list of all previous ColdFusion 11 updates, refer to the update page.

Bugs fixed

For the detailed list of bugs fixed in this update, refer to the list of bugs fixed.

Prerequisites

1. On 64-bit computer, use 32-bit JRE for 32-bit ColdFusion and 64-bit JRE for 64-bit ColdFusion.
2. If the ColdFusion server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties below in the jvm.config for a stand-alone installation, or corresponding script file for JEE installation.
   • http.proxyHost
   • http.proxyPort
   • http.proxyUser
   • http.proxyPassword
3. For ColdFusion running on JEE application servers, stop all application server instances before installing the update.

Installation

For instructions on how to install this update, see Server Update section. For any questions related to updates, refer this FAQ.

• The update can be installed from the Administrator of a ColdFusion server instance or through the command-line option.
• Windows users can launch the ColdFusion Administrator using Start > All Programs > Adobe > Coldfusion 11 > Administrator.
• If you get the following error when installing the update using the Download and Install option, ensure that the folder{cf_install_home}/{instance_name}/hf_updates has write permission: "An error occurred when performing a file operation write on file {cf_install_home}/{instance_name}/hf-updates/hotfix_00013.properties".
• From Update 5 onwards, the connector configuration files are backed up at {cf_install_home}/config/ wsconfig /backup. Add back any custom changes made to the worker.properties file after reconfiguring the connector.

Installing the update manually

1. Click the link to download the update JAR,
2. Execute the following command on the downloaded JAR. Launch the command prompt to apply the update. You must have privileges to start or stop ColdFusion service and full access to the ColdFusion root directory.

    Windows: <cf_root>/jre/bin/java.exe -jar <jar-file-dir>/hotfix_013.jar

    Linux-based platforms: <cf_root>/jre/bin/java -jar <jar-file-dir>/hotfix_013.jar

Ensure that the JRE bundled with CF is used for executing the downloaded JAR. For standalone CF, this must be at, <cf_root>/jre/bin.

For further details on how to manually update the application, see the help article.

Post installation

After applying this update, the ColdFusion build number should be 11,0,13,303668.

Uninstallation

To uninstall the update, do one of the following:

• In ColdFusion Administrator, click Uninstall in Server Update > Updates > Installed Updates.
• Run the uninstaller for the update from the command prompt. For example, java -jar {cf_install_home}/{instance_home}/hf_updates/hf-11-00013/uninstall /uninstaller.jar

If you can't uninstall the update using the above-mentioned uninstall options, the uninstaller could be corrupted. However, you can manually uninstall the update by doing the following:

1. Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
2. Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-11-00013}/backup directory to {cf_install_home}/{instance_name}/

Remember

1. In the ColdFusion Administrator, if you see the update listed in both Available Updates and Installed Updates, it could be a caching issue. Do the following:
   1. Navigate to Server Update > Updates > Available Updates and click Check For Updates.
   2. Press Ctrl+F5 to remove the bulb notification from the top banner of the ColdFusion Administrator.
2. If ColdFusion server doesn't start automatically (ps -ef | grep -i coldfusion command indicates ColdFusion is running, but the ColdFusion Administrator cannot be accessed), restart the server manually after applying the update. This issue is rare and occurs on few Unix or Linux-based operating systems (when buffer allocation size of the machine console is almost zero).