INC-204045 · Issue 694323
Signature map updated for fetching keys
Resolved in Pega Version 8.6.3
MFA login worked with SAML 2.0 when the certificate was disabled but failed when the certificate was enabled in Auth Service. The error " "Signature algorithm is null" appeared. This has been resolved by updating the signature map to ignore case sensitivity while fetching keys.
INC-204897 · Issue 696148
Log4j file security vulnerability issue addressed
Resolved in Pega Version 8.6.3
A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .
SR-B45056 · Issue 328736
XSS filtering added to getClassOfPageReference
Resolved in Pega Version 7.4
XSS filtering has been added to the URL produced when using getClassOfPageReference.
SR-B45056 · Issue 330368
XSS filtering added to getClassOfPageReference
Resolved in Pega Version 7.4
XSS filtering has been added to the URL produced when using getClassOfPageReference.
SR-B74553 · Issue 326255
Refined accessgrouplist checks
Resolved in Pega Version 7.4
Following a system modification that changed the property used to populate the access groups list to match that on clipboard (correct value), a previously unseen issue was uncovered where all the division and organization AGs were being added to the list. This has been addressed by updating the code to add the applications on division and organization only when there is no default selected at the operator. If there is some application selected as default at the operator, then the division or organization applications will not be added. If there is nothing selected at operator, then a check for division will be made, and if there is nothing selected at division then organization will be checked.
SR-B78496 · Issue 327358
Refined accessgrouplist checks
Resolved in Pega Version 7.4
Following a system modification that changed the property used to populate the accessgroups list to match that on clipboard (correct value), a previously unseen issue was uncovered where all the division and organization AGs were being added to the list. This has been addressed by updating the code to add the applications on division and organization only when there is no default selected at the operator. If there is some application selected as default at the operator, then the division or organization applications will not be added. If there is nothing selected at operator, then a check for division will be made, and if there is nothing selected at division then organization will be checked.
SR-B81365 · Issue 332518
Enhanced security for IAC gadget
Resolved in Pega Version 7.4
The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.
SR-B81365 · Issue 331996
Enhanced security for IAC gadget
Resolved in Pega Version 7.4
The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.
SR-B82500 · Issue 331560
Enhancement to support external delegated authentication via custom authentication
Resolved in Pega Version 7.4
OAuth 2.0 configuration has been embedded into the HC mobile app to provide an infrastructure for REST services to be authenticated by an external token which has been issued by third party identity provider. When Pega receives a token, it then contacts the identity provider's token introspection and userinfo endpoint to validate the token and subsequently establish an identity. The new authentication activity has been shipped with the name 'pyPerformDelegatedAuthentication' that can be attached to any Authentication service data instance.
SR-B82500 · Issue 332132
Enhancement to support external delegated authentication via custom authentication
Resolved in Pega Version 7.4
OAuth 2.0 configuration has been embedded into the HC mobile app to provide an infrastructure for REST services to be authenticated by an external token which has been issued by third party identity provider. When Pega receives a token, it then contacts the identity provider's token introspection and userinfo endpoint to validate the token and subsequently establish an identity. The new authentication activity has been shipped with the name 'pyPerformDelegatedAuthentication' that can be attached to any Authentication service data instance.