Release Notes V10.1.0 Fix Pack 3
A summary of changed or new features and enhancements included in Remote Control Fix Pack 3.
Remote Control V10.1.0 Fix Pack 3 GA
- AES 256 cryptographic algorithm enabled by default
With the new version of IBM WAS Liberty, AES 256 is now the default cryptographic algorithm, replacing AES 128 for stronger security. To ensure seamless operation and leverage this enhanced encryption, we highly recommend you regenerate your SAML Metadata.
If FIPS is enabled, this step is mandatory. You must regenerate your SAML Metadata to encrypt passwords with AES 256, as AES 128 encrypted passwords are no longer supported.
You can regenerate the SAML Metadata during the Remote Control Server upgrade procedure by selecting the appropriate flag. After regenerating the metadata, please remember to re-register with your Identity Provider.
- Install Shield 2024 adoption
Install Shield 2024 has been used to build the Windows installers for the Controller, Target, Broker, and Gateway.
- Update of IBM WAS Liberty, IBM Java, and OpenSSLThis product release adopts the following:
- IBM WAS Liberty version is 25.0.0.6
- IBM Java SDK version 8.0-SR8-FP45
- IBM Semeru JRE version 8.0u452
- OpenSSL version 3.4.1
- CVE-2025-31965 – Standard users could view some Admin pages into the Server. Affected components: Remote Control Server.
- CVE-2024-13176 – Timing side-channel in ECDSA signature computation (OpenSSL).
- Affected components – Remote Control Target, Remote Control Broker, Remote Control Gateway.
- KB0119265 – Remote control access shows a gray screen when connecting.
- KB0119643 – Broker crash issue.
- KB0121115 – Self-signed error for Root certificate with Reverse Proxy enabled on the Broker.
- KB0120278 – Login disclaimer of the RC Server allows to bypass.
- KB0122763 – Increased CPU usage of the RC Server with duplicate GUIDs of unattended Targets.