Bug ID
ColdFusion (2018 release) Update 10
If you are applying Update 10 without applying Update 8, follow the Post Installation steps mentioned for Update 8.
Note: If you are already on Update 8, you can apply Update 10 without performing any intermediary steps.
If you are updating via ColdFusion Administrator:
The minimum update versions are Update 4 or higher for ColdFusion (2018 release), due to a recent change in code signing certificate.
These are mandatory pre-requisites before updating.
The updates below are cumulative and contain 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 install previous updates, see ColdFusion (2018 release) Updates.
ColdFusion (2018 release) Update 10 (release date, 14 July, 2020) addresses vulnerabilities that are mentioned in the security bulletin, APSB20-43, and a few other issues.
For security reasons, we strongly recommend that you delete the file after the car file deployment.
On the Archive wizard UI, we've added a text accordingly.
Bug ID |
Description |
Component |
---|---|---|
Unexpected memory issues in Redis. The application runs on ColdFusion (2018 release) Update 5 and Redis 5.0.5 on AWS managed service. |
Caching |
|
When monitoring is enabled for a server in Performance Monitoring Toolset, cfthread tags fail to execute intermittently. |
Performance Monitoring Toolset |
|
After updating ColdFusion, a few applications started to behave unexpectedly. |
Security |
|
Intermittent StackOverflowError exception when launching some pages. |
Security |
|
There are numerous calls to Redis in a time interval. |
Performance Monitoring Toolset |
|
CFHTTP calls with proxyserver produce Error 404. |
HTTP |
For instructions on how to install this update, see Server Update section. For any questions related to updates, see this FAQ.
Windows: <cf_root>/jre/bin/java.exe -jar <jar-file-dir>/hotfix-010-320417.jar
Linux-based platforms: <cf_root>/jre/bin/java -jar <jar-file-dir>/hotfix-010-320417.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.
After applying this update, the ColdFusion build number should be 2018,0,10,320417.
Post installation, we recommend rebuilding or reconfiguring your connector.
Note: This holds true only if you have applied Update 10 without applying Update 8.
If you see Error 503 or Error 403 when firing up your websites, see the troubleshooting steps.
After you've installed Update 10 (with a pre-configured connector), and have locked down the server using the Auto-Lockdown installer, you may encounter Error 403 forbidden, when accessing the web pages.
To fix this issue, follow the steps mentioned below:
Locations of files
File |
Location |
---|---|
server.xml |
{cf.instance.home}\runtime\conf |
AJP connector in server.xml |
AJP connector has protocol attribute set as AJP/1.3. For example, <Connector port="8018" protocol="AJP/1.3" packetSize="65535" redirectPort="8451" tomcatAuthentication="false" maxThreads="500" connectionTimeout="60000" secret=”abcd” /> |
secret in server.xml |
The secret value in server.xml is present in the Connector Node with the attribute name as secret. For example, <Connector port="8018" protocol="AJP/1.3" packetSize="65535" redirectPort="8451" tomcatAuthentication="false" maxThreads="500" connectionTimeout="60000" secret=”abcd” /> |
workers.properties in IIS |
{cf.home}/config/wsconfig/<magic_folder_number> |
workers.properties in Apache |
APACHE_HOME/conf/ |
secret in workers.properties |
worker.cfusion.secret=<secret> |
To uninstall the update, perform one of the following:
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:
Sign in to your account