How can I fix the Apache Commons Collection 3.1 Java object de-serialisation vulnerability if I have CA SSO 12.52 SP1?

Document ID:  TEC1857407
Last Modified Date:  06/15/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Single Sign-On

Components

  • SITEMINDER -POLICY SERVER:SMPLC
Introduction:

Apache have reported a vulnerability in the Commons Collection library as per

https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread 

This affects the 3.1 version of the library and it is corrected in version 3.2.2 and 4.1

According to the release notes for CA Single Sign On 12.52 SP1

https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/third-party-software-acknowledgments

Common Collections 3.1 is used here

 

Question:

Is there any fix to address the Commons Collection library java de-serialisation vulnerability discovered in version 3.1 for CA Single Sign On 12.52 SP1?

Answer:

This has been fixed and verified in R12.52 SP1 CR06 for Policy Server, AdminUI and Secure Proxy Server in a variety of systems. Please upgrade to this release to correct this.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >