SR-B91752 · Issue 340794
TrackSecurityChanges passes correct values for page groups
Resolved in Pega Version 7.4
The pzTrackSecurityChanges Utility is called from the TracKSecurityChangesLogic activity whenever the value changes for an audited property. For this function, current value and previous value are passed from the clipboard. However, in cases of page groups, the parent property was being passed instead of the current and previous values. This has been fixed.
SR-B93715 · Issue 344806
Apache Groovy updated
Resolved in Pega Version 7.4
Apache Groovy has been updated to 2.4.4 for improved security.
SR-B93934 · Issue 340753
Sensitive handling added for validation of encrypted SOAP
Resolved in Pega Version 7.4
The WSS4J library was not calculating the processing actions validation on encrypted SOAP messages correctly after the message's security requirements were already processed by the library. This means that the verification of signature or decryption or any other actions worked and the necessary security processors were engaged correctly, however the check was failing during the last leg of the processing actions validation. Since the action matching is of less significance, the validation for actions will be relaxed in situations where the ws-security config is signature and encryption and/or timestamp.
SR-B95798 · Issue 344526
XSS filtering added to GetTour
Resolved in Pega Version 7.4
Cross scripting filtering has been added to pxGetTour java step 7, which prepares JSON.
SR-C1107 · Issue 351146
Oauth tokens obtained on login timeout
Resolved in Pega Version 7.4
When the client idle time expires, the user must perform a login in order to get back into the application. If OAuth is being used for authentication there is no need to re-send the credentials to NetIQ if neither the refresh token nor access token are expired yet, but the hybrid client was repeating the ROPC flow and obtaining a new refresh token each time the user logged in after the client idle timeout expires. With this change, the tokens are obtained on login timeout. There will be a further update targeted for the next release to show the lock screen and not log the user out.
SR-C1107 · Issue 351606
Oauth tokens obtained on login timeout
Resolved in Pega Version 7.4
When the client idle time expires, the user must perform a login in order to get back into the application. If OAuth is being used for authentication there is no need to re-send the credentials to NetIQ if neither the refresh token nor access token are expired yet, but the hybrid client was repeating the ROPC flow and obtaining a new refresh token each time the user logged in after the client idle timeout expires. With this change, the tokens are obtained on login timeout. There will be a further update targeted for the next release to show the lock screen and not log the user out.
SR-C147 · Issue 343884
Security improvements for generateCellContent RUF
Resolved in Pega Version 7.4
Code changes have been made to improve security for getting the parameter value in the generateCellContent RUF.
SR-C1787 · Issue 346038
XSS filtering added for insHandle
Resolved in Pega Version 7.4
XSS filtering has been added for the inshandle parameter in the downloadFile activity.
SR-C1787 · Issue 320158
Exception message will not include invalid filename
Resolved in Pega Version 7.4
To enhance security, the exception message In the activity Rule-File-Binary.downloadFile will not display the invalid filename.
INC-128533 · Issue 588007
Property check handling updated for Ajax requestor
Resolved in Pega Version 8.6
SECU0001 alerts were seen when submitting a case in the interaction portal. Logging indicated the errors were related to the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties which are included in an Ajax request when they exist in the DOM and the 'pyGeolocationTrackingIsEnabled' when rule is true. The error was traced to a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties have been added to an allow list to handle the unexpected properties check.