If you have
Последнее обновление
21 мая 2021 г.
ColdFusion (2016 release) Update 11
Примечание.
The updates below are cumulative and contains all updates from previous ones. If you are skipping updates, you can apply the latest update, not those you are skipping. Further, you must take note of any changes that are implemented in each of the updates you are skipping.
To see a list of all previous ColdFusion updates, refer to the update page.
Updates in this release
ColdFusion (2016 release) Update 11 (release date, 11 June, 2019) includes the following changes:
- Addresses security vulnerabilities mentioned in the security bulletin APSB19-27.
- Added support for the function FileAppend.
Updates to LiveCycle Data Services
Remote access to the Adobe LiveCycle Data Management feature has been disabled.
To mitigate potential security risks, admins are recommended to first implement access controls to the RMI port via the host or network firewall.
If you want to enable LCDS after installation, follow the steps below:
- Open the file jvm.config and add the flags:
- -Dcoldfusion.rmi.enable=true
- -Dcoldfusion.rmi.enablelcds=true
- Launch ColdFusion Administrator and enable the option, Enable Remote Adobe LiveCycle Data Management access., if it is not enabled already.
- Restart ColdFusion.
|
|
Then |
|---|---|
|
Not enabled the option Enable Remote Adobe LiveCycle Data Management access before applying the update, |
After the update, if you enable the option Enable Remote Adobe LiveCycle Data Management access, the following error message appears:: Error attempting to update settings: RMI for LCDS has been disabled. Set coldfusion.rmi.enable and coldfusion.rmi.enablelcds JVM flags as true in jvm.config file and restart the server. NOTE: The error message only appears if you did not set the flags in jvm.config, as mentioned in the previous step. |
|
Enabled the option Enable Remote Adobe LiveCycle Data Management access before applying the update, |
LCDS may not work as expected. See the section above for more information. |
Updates to JNBridge
In this update, remote access to .NET to Java side for JNBridge has been disabled.
To mitigate potential security risks, admins are recommended to first implement access controls to the JNBridge port via the host or network firewall.
To grant access to the port,
- Take a back up of the file neo-dotnet.xml (CF_HOME/cfusion/lib).
- Add the following flags in neo-dotnet.xml:
- <var name='hostIP'><string>0.0.0.0</string></var>
- <var name='ipWhitelist'><string>127.0.0.1;<IP of the machine where the remote .NET service is running></string></var>
- <var name='hostIP'><string>0.0.0.0</string></var>
- Restart ColdFusion.
Примечание.
For the security fixes in Update 7 and above to take effect, ColdFusion must be on JDK 1.8.0_121 or higher.
Примечание.
To view all ColdFusion (2016 release) updates, see the Updates page.
Bugs fixed
For the detailed list of bugs fixed in this update, refer to Bugs fixed list.
Prerequisites
- On 64-bit computer, use 32-bit JRE for 32-bit ColdFusion and 64-bit JRE for 64-bit ColdFusion.
- 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
- 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, see this FAQ.
- The update can be installed from the Administrator of a ColdFusion instance or through the command-line option.
- Windows users can launch the ColdFusion Administrator using Start > All Programs > Adobe > Coldfusion 2016 > Administrator.
- Microsoft Windows 7, Windows 8, Windows 10, Windows Server 2008, and Windows Server 2012 users must use the “Run as Administrator” option to launch wsconfig tool at {cf_install_home}/{instance_name}/runtime/bin.
- 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_011.properties".
- 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
- Click the link to download the JAR.
- Execute the following command on the downloaded JAR. 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-011-314546.jar
Linux-based platforms: <cf_root>/jre/bin/java -jar <jar-file-dir>/hotfix-011-314546.jar
Ensure that the JRE bundled with ColdFusion is used for executing the downloaded JAR. For standalone ColdFusion, this must be at, <cf_root>/jre/bin.
Install the update from a user account that has permissions to restart ColdFusion services and other configured webservers .
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 2016,0,11,314546.
Uninstallation
To uninstall the update, perform 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-2016-00011-314546/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:
- Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
- Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-2016-00011-314546}/backup directory to {cf_install_home}/{instance_name}/