Table of Contents

• Fix list
• Downloading the cumulative fix
• Upgrading IBM RPA 11.0.0.x to IBM RPA 11.0.0.10
• Resolving issues after upgrading
  • "Dual navigator" issue
  • Connectivity issues
• Post-upgrade tasks
• Additional information
• Trademarks and service marks  

Fix list

APAR	Security APAR	Behavior Change	Title
Security Fixes
JR60971			SECURITY APAR CVE-2019-4298 - IBM RPA USES A HIGH-PRIVILEGE POSTGRESQL ACCOUNT FOR DATABASE ACCESS
JR60982			SECURITY APAR - CVE-2019-4297 - IBM RPA IS VULNERABLE TO LDAP INJECTION
JR60985			SECURITY APAR - CVE-2019-4295 - IBM RPA CREDENTIAL VAULT MIGHT LEAK SECRETS ON THE CLIENT
JR60991			SECURITY APAR - CVE-2019-4299 - THE IBM RPA CLIENT SECURITY TOKEN IS WRITTEN TO THE CLIENT LOG FILE
JR60992			SECURITY APAR - CVE-2019-4296 - IBM RPA PRINTS EMAIL CONTENT TO THE CLIENT DEBUG LOG FILE
JR61043			SECURITY APAR - CVE-2019-4337 - IBM RPA IGNITE NODES ARE MISSING AUTHENTICATION
JR61053			SECURITY APAR - CVE-2019-4336 - IBM RPA FORGOT-PASSWORD FUNCTION IS VULNERABLE TO BRUTE-FORCE ATTACKS
Other Fixes
JR60564			IBM RPA INSTALLER CREATES XXX.TMP.BAT FILES THAT MCAFEE ANTIVIRUS BLOCKS
JR60823			TASK SCHEDULES DISAPPEAR AND LATER REAPPEAR
JR61013			THE OBJECT CLONING COMMAND IN IBM RPA FAILS WITH "UNABLE TO PERFORM LEFT CLICK ACTION"
JR61029			THE CONTROL ROOM DASHBOARDS ARE BLANK AFTER YOU UPGRADE TO IBM RPA 11.0.0.4 INTERIM FIX 002
JR61225			AN ERROR OCCURS WHEN YOU TRY TO IMPORT A BAPI FROM SAP

None

 11.0.0.2 fixes:

APAR	Security APAR	Behavior Change	Title
JR59512			SECURITY APAR CVE-2018-1552: ANY FILE TYPE CAN BE UPLOADED TO THE CONTROL ROOM
JR59621			YOU CANNOT RE-USE A TERMINAL EMULATOR SESSION IN A CHILD TASK BOT
JR59920			YOU SEE WRONG FILE NAMES AFTER YOU EXTRACT A ZIP FILE WITH JAPANESE CHARACTERS USING THE UNZIP COMMAND
JR60077			SECURITY APAR CVE-2018-1876: In certain cases, the password is displayed in log files
JR60078			SECURITY APAR CVE-2018-1877: Passwords are stored in plain text post Control Room Installation
JR60082			SECURITY APAR CVE-2018-1878: Control room divulges information (such as server type) in an error page

11.0.0.1 fixes:

Downloading the cumulative fix

The cumulative fix is available for download from IBM Support Fix Central. The fix contains separate upgrade packages for IBM RPA Control Room and IBM RPA clients.

Download packages

How critical is this fix?
Recommended

Upgrading IBM RPA 11.0.0.x to IBM RPA 11.0.0.10

During the upgrade process, the previous version of IBM RPA is removed and then IBM RPA 11.0.0.10 is installed.

Before you upgrade

• You are strongly advised to back up your existing IBM RPA environment so you can roll back your environment if you encounter issues during or after the upgrade.
• If you're using SQL server 2014, install the SQL Server Express 2014 SP1 to upgrade the default SQLEXPRESS instance.
• If you're intending to move your Bot Insight metadata databases from PostgreSQL Server to Microsoft SQL server during the upgrade, see Release Note 11.0.0.x: Moving Bot Insight metadata databases from PostgreSQL Server to Microsoft SQL Server for more information.

Upgrading your installation

To upgrade IBM RPA 11.0.0.x to 11.0.0.10, follow the instructions in Installing fix packs. There are separate procedures for upgrading IBM RPA Control Room and the IBM RPA clients. Upgrade Control Room before you upgrade Bot Creator and Bot Runner clients.

Resolving issues after upgrading

The "dual navigator" issue

You might encounter the “dual navigator" issue in the upgraded control room. This is a known issue and is documented on the Automation Anywhere web site, which outlines a suggested resolution. This issue was first found in IBM RPA 11.0.0.5 (AA 11.3.2) and might still occur when upgrading to the latest version of IBM RPA. The root cause of the issue is now known and IBM is working closely with Automation Anywhere to provide a fix in a future IBM RPA update.

Connectivity issues

If you experience problems connecting to Control Room after you upgraded an IBM RPA Enterprise express installation, follow these steps to resolve problems related to HTTP port settings:

1. Open the C:\Program Files\Automation Anywhere\Enterprise\traefik\traefik.toml file and your backup copy of the aae-installsummary.html file.
2. Compare the HTTP port settings in both files. If the port number differs, change the value in the traefik.toml file to the value in the aae-installsummary.html backup file.
3. Save the traefik.toml file and try connecting to Control Room again.