Documentation

 

 

9.1.0 Hotfixes

The following is a list of hotfixes for SecureAuth IdP version 9.1.0.

Release No.Release DateRef IDIssue
9.1.0-58

24-Jul-2020

EE-1778

OIDC / OAuth2 Workflow Session Cleanup – OIDC queries in OAuth workflows are not read correctly when a user has two browser tabs open when authenticating into a resource.

Install this fix if you have:

  • OIDC / OAuth2 integrations
EE-1815

Security Fix – Resolved XSS security vulnerability in path resolution.

CVSS Score: 5.3

This hotfix is required for all customers on SecureAuth IdP version 9.1 to ensure the security of the appliance.

EE-1830

WS-Fed and SAML Valid Hours Issue – When the SAML Valid Hours is set to a non-integer value, it does not work for WS-Fed integrations.

Install this fix if you have:

  • WSFed integrations
9.1.0-5729-Jun-2020EE-1644

Security Fix – Implemented additional input validation to prevent double curly brackets ( {{ or }} ) in form input fields, including the UserID field.

CVSS Score: 2.0

This hotfix is required for all customers on SecureAuth IdP version 9.1 to ensure the security of the appliance.

9.1.0-5612-Jun-2020EE-1690

Updates to Audit Logging for OIDC – Audit Logging updated for OIDC workflows to provide more clarity.

Install this hotfix if you have:

  • OIDC integrations
EE-1781

Transformation Engine Issue – Resolves issue in which the Transformation Engine did not work correctly when used with WS-Federation.

Install this hotfix if you have:

  • Transformation Engine enabled and configured
9.1.0-5528-Feb-2020EE-1511

Session Timeout Length – Increased session timeout length to accommodate specific use cases.

Install this hotfix if you have:

  • A need for longer session timeout lengths
EE-1519

SameSite Cookie attribute support – Required for compatibility with Google Chrome 80.

This hotfix is required for all 9.1 appliances.

Ensure that the Microsoft .NET patch is applied prior to installing this hotfix. Read https://support.secureauth.com/hc/en-us/articles/360038330652 for more information.

EE-1558

OTP Value Reusability – Resolves issue when using the API OTP validate endpoint, it was possible to reuse the same OTP at a later time.

Install this hotfix if you have:

  • Authentication API enabled
  • Any OTP MFA method enabled
9.1.0-5412-Dec-2019EE-1429

Enhanced Device Recognition Logging – Device Recognition logging enhanced to make the results of the analysis clearer.

Install this hotfix if you have:

  • Realms that use Device / Browser Fingerprinting as the Client Side Control (Workflow configuration)
EE-1469

Device Recognition NULL Values – Resolves issue where “NULL” is returned in the Device Recognition profile as a score for a field, and the profile fails to match.

Install this hotfix if you have:

  • Realms that use Device / Browser Fingerprinting as the Client Side Control (Workflow configuration)
EE-1499

API Update for Hashed PIN – Using the API to update a user’s PIN no longer fails when the PIN is stored hashed.

Install this hotfix if you have:

  • PIN enabled as an MFA method
  • PIN hashing turned on
  • IdM API enabled for account update
EE-1512

mS-DS-ConsistencyGUID Support for Office 365 Integration – The mS-DS-ConsistencyGUID attribute is now supported by SecureAuth IdP to be used as the ImmutableID value for integrations with Office 365.

Install this hotfix if you have:

  • Integration with Office 365
  • Issues using objectGUID as the ImmutableID
9.1.0-53

15-Oct-2019

EE-1342

Cross-Site Request Forgery Vulnerability – CSRF tokens have been added to the administrative web interface.

CVSS Score: 4.7

This hotfix is required for all customers on SecureAuth IdP version 9.1 to ensure the security of the appliance.

EE-1336

RBAC Group List – Resolves issue where a list of groups are created for a specific role type and not all groups were available to select, even after typing the full group name.

Install this hotfix if you have:

  • RBAC rules configured
  • High number of Active Directory groups (reported by customers with 1000+ groups)
EE-1363

Support for AssertionConsumerServiceIndex (SAML) – SecureAuth IdP now supports AssertionConsumerServiceIndex for SAML integrations.

Install this hotfix if you have:

  • SAML integrations that require AssertionConsumerServiceIndex instead of AssertionConsumerServiceURL, for example: Cisco Jabber

For instructions about applying the hotfix for this feature, see SAML integrations using AssertionConsumerServiceIndex hotfix

9.1.0-5213-Aug-2019EE-1272

AuthCode Validity Issue – Only one AuthCode can be used in OIDC workflows for a client to obtain an access_token.

Install this hotfix if you have:

  • OIDC integration realms configured in the Post Authentication tab
  • Consent Storage enabled in OIDC integration (required for this verification)
EE-1312

Cross-Site Request Forgery Vulnerability – CSRF tokens have been added to the administrative web interface.

CVSS Score: 6.7
NOTE: This fix applies ONLY to the Web Admin application.

This hotfix is required for all customers on SecureAuth IdP version 9.1 to ensure the security of the appliance.

EE-1315

Arbitrary File Upload Vulnerability – An authenticated privileged user can no longer upload arbitrary file types.

CVSS Score: 8.4
NOTE: This vulnerability applies to the Web Admin application ONLY.

This hotfix is required for all customers on SecureAuth IdP version 9.1 to ensure the security of the appliance.

9.1.0-5125-Jul-2019EE-1287

Device Recognition Data Storage Issue – When storing the Device Recognition Profiles (Device Fingerprints) in the SQL data base in JSON format, all data is now correctly stored.

Install this hotfix if you have:

  • SQL data base integrated with SecureAuth IdP on the Data tab
  • JSON selected as the Data Format in the Profile Fields section of the Data tab
  • Device / Browser Fingerprinting selected as the Client Side Control on the Workflow tab
  • SQL Tables and Stored Procedures using JSON format
9.1.0-5026-Jun-2019EE-1220

New userAccountControl Values – SecureAuth IdP now has the most up-to-date userAccountControl values to ensure that certain account statuses are handled appropriately in transactions between LDAP providers and SecureAuth IdP.

Install this hotfix if you have:

  • LDAP directory integrations such as Active Directory (AD) and so on
  • Help Desk functionality to manage LDAP user accounts by means of SecureAuth IdP
9.1.0-4903-Jun-2019EE-1199

Third-party JavaScript Libraries Vulnerability – jQuery, Bootstrap, and AngularJS have been upgraded due to a flaw in these libraries that may result in XSS.

CVSS Score: 5.2

This hotfix is required for all customers on version 9.1 to ensure the security of the appliance.

9.1.0-4810-May-2019EE-1179Inline Password Reset Issue – Using the 2016 Light Theme, the Inline Password Reset pages now work as expected for all use cases.
9.1.0-4714-Mar-2019EE-1131Device Fingerprint Space Issue The Device Fingerprint cookie name now parses correctly if a space was present in the generated cookie name.
EE-1069Logging Updates – Updates to SecureAuth IdP logs to ensure security.

EE-1028
EE-1120

URL Encoding Updates – Updates to URL encoding to ensure security.
9.1.0-4630-Nov-2018

EE-930Log Database Collection – SecureAuth IdP no longer stops creating log entries when records grow very large (2,147,483,647+).
EE-986Google ID Social Login – Issue resolved in which Google API changes caused SecureAuth IdP’s social login feature for Google Apps to stop working.
EE-991Begin Site Redirect Encoding – Begin site redirect is no longer double encoding the request query which had been causing the realm to break and the workflow to halt.
9.1.0-4506-Sep-2018

EE-906eDirectory Group Issue – Error no longer occurs when attempting to add a user to a group in eDirectory via the Create User function.
EE-123Timeout Message Display – When users are logged out of Secure Portal based on timeout, the notification now displays the timeout message configured on the realm.
9.1.0-4427-Jul-2018

EE-847OIDC Subject Claim Issue – Introspection endpoint was failing when access token subject claim contained a client ID.
9.1.0-4221-May-2018

EE-786OIDC EndSession Redirect – Redirect and session end was not occurring due to the 'post_logout_redirect_uri' parameter requiring the presence of the 'id_token_hint' parameter. Redirect now functions with the presence of 'client_id' only, and does not require 'id_token_hint'.
9.1.0-4107-May-2018EE-746

Create User Failure for eDirectory – Create User page integrated with eDirectory was not functioning due to hardcoded attribute information.

NOTE: This fix enables the creation of users, but certain functionalities of the page are not supported for eDirectory at this time.

EE-749

Proxy Settings for OIDC Encryption Key Retrieval – Proxy settings configured in SecureAuth IdP are not applied when retrieving OIDC encryption keys.

EE-718

Create User Group Designation SQL – Create User page with SQL data store integration does not associate users to groups on the page during creation.

NOTE: This fix requires a new stored procedure provided by SecureAuth Support (see contact information below).

9.1.0-4026-Apr-2018EE-731

Novell eDirectory Lookup – During login, a user’s profile was not accessed successfully and the self-service password reset was unsupported.

EE-642Mobile QR Code Enrollment – When device limitation is enforced, false errors would occur during QR code enrollment.
EE-703SA Cloud Timeout and Fail Open – Due to extended timeouts and no fail open functionality, users were unable to log in when SA Cloud services are down.
EE-446Errant Calls to Invalid URLs – Calls made for IP Evaluation were hitting the wrong endpoint URLs.
EE-629Bad IPv6 Handling – During Adaptive Authentication analysis, IPv6 calls created issues with the evaluation.
9.1.0-39 or earlierVariousEE-559JWT Missing Claim – In OAuth 2.0 Client Credential Flow, the ‘sub’ (subject) claim was missing in the JWT.
EE-586Encryption Functionality – Encryption functionality was static due to the disability of this feature.
EE-533OTPValidateThrottle PUT Call – OTPValidateThrottle PUT call was resetting the count for both values (Select vs. Validate counts).
EE-514
EE-521
Self-service PIN Update – The Update button needed two clicks to save new PIN information.
EE-470RADIUS Server Timeouts – RADIUS Server requests were timing out when under a high load.
EE-482Slow Response – When connected to a Syslog Server, too many UDP clients created a massive slow down.
EE-417Tivoli Directory Device Recognition – Device / Browser Profiles were not accurately saved to Tivoli user profiles.
EE-483Link-to-Accept with Proxy – Link-to-Accept did not properly go through the configured proxy settings (both SMS and email).
EE-480Device Recognition on IE10 – PixelRatio property analyzed for fingerprinting was unsupported in IE10 and therefore returned a null response and invalid browser profile.
EE-464YubiKey Validation Call Failure – API calls to validate the YubiKey login fail due to character limitations in the string.
EE-376Account Management Error – Updating the OATH Seed on the Account Management page created an error due to split directory integrations for membership and profile.
EE-429SMTP Timeout Errors – Using the Authentication API to request OTP emails, the user experienced SMTP timeout errors.
EE-366HID Token Read Failure – Login process was unable to read the OATH Seed from an HID token for MFA, and SecureAuth IdP was unable to read the OATH Seed from HID token for post-authentication.
EE-3372016 Light Theme Login Page – When pasting a password (from password manager, for example), the Submit button did not change color and the mouse cursor showed the ‘no entry’ icon. Clicking the button worked, but visually appeared as though it would not.
EE-329Verbiage Customizations – When a user’s browser is not set to English and the preferred language is not selected in the SecureAuth IdP configuration, then the browser defaulted to English, but without the verbiage customizations made in the Web Admin.
EE-345Invalid Username not Updating – With workflow type set to Username & Password, when the user entered an invalid username and then corrected it, the username was still considered invalid and the page reverted the text back to the original invalid entry.
EE-328OTPValidate Throttle not Counting – Instead of creating a unique counter for OTPValidate, the MultiFactorIntervalThrottle counter was used instead.
EE-320Login for Windows UI – Various UI defects were resolved in Login for Windows.
EE-303Username Overflow – On the Account Management page, the username overflowed into the next text box.
EE-295OIDC Redirect URI with Localhost – For OIDC integrations, the Redirect URI did not support localhost.
EE-248NumberProfile API Server Error – Requests to the phone number analysis endpoint with an invalid number (e.g. 123456789) generated a server error response.
EE-265Password Requirements for Create User Page – Password requirements configured on the Web Admin were not applied to the Create User page.
EE-263Unwanted Verbiage on Page – A flag on a page displayed unwanted verbiage on client-side pages.
EE-203Duplicate Knowledge Based Questions – Users were able to select the same KBQ multiple times, thus only having one question to answer for Multi-Factor Authentication.
EE-255No Automatic Redirect – Users were not automatically redirected from SecureAuth IdP with an OIDC token to the relaying application.
EE-212Invalid User Error – LDAP users attempting to log in continually received an “Invalid User” error.
EE-202OATH Token Invalidation – After upgrading to version 9.1, existing OATH Tokens were no longer valid and required re-provisioning.
IDP-1721Login for Windows Configuration – Configuration settings for new Login for Windows product were not available in the Web Admin.
EE-183FIPS Compliance – SecureAuth IdP updates were made for FIPS Compliance requirements.
IDP-2554Admin API HMAC Authentication – It was possible to remove HMAC authentication from the Admin API.
EE-119
EE-175
Authentication API Throttling – The Multi-Factor Throttling count doubled based on selection and validation of the OTP, thereby rendering the configuration inaccurate.
IDP-2524Web.config URL Update – Values for some URLs were incorrect in the web.config.
IDP-2486Compilation Error – The SISU code file contained a compilation error.
IDP-2516ChangePassword Error – Username was missing a domain slash for Change Password via the API.
IDP-2497Link-to-Accept UI Update – Color of the button was incorrect.
IDP-2512Authentication API OATH Token Failure – OATH Token was not working as a viable Multi-Factor Authentication option via the Authentication API.

Affected SecureAuth IdP Version(s): 9.1

Support Information: Contact SecureAuth Support (support.secureauth.com, support@secureauth.com, or 1-866-859-1526) to have the latest hotfix installed on your SecureAuth IdP v9.1.x appliance.

  • No labels