RSA BSAFE Dual_EC_DRBG vulnerability in CA Single Sign-on

Document ID : KB000028796
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:
The default random number generator, Dual_EC_DRBG, in RSA BSAFE libraries was compromised. What are the best practices and how to avoid use of these compromised libraries?


Answer:
RSA BSAFE is a FIPS 140-2 validated cryptography library offered by RSA Security. From 2004 to 2013, the default cryptographically secure pseudorandom number generator (CSPRNG) in BSAFE was Dual_EC_DRBG, which contained a backdoor from NSA. CA Single Sign-On uses RSA libraries through ETPKAI or CAPKI as well as directly. These library files are shipped with the product but only used in case of FIPS only installation types.

CA Technologies has developed a fix to address this issue by removing ECDRBG algorithm and using HMAC DRBG 128 as an alternate algorithm for random number generator.

  • CA Single Sign-On 12.52
    In this release, the ECDRBG library files have been removed and the HMAC DRBG 128 has been added as default random generator. If you are upgrading to 12.52 version then the upgrade process will take care of removing the library files. 

 

  • CA Single Sign-On 12.5 and 12.51
    If you are on these releases or upgrading to these releases, please follow these steps:

 

    1. Delete the ECDRBG library file from the installation directory:
      • On Windows: ccme_ecdrbg.dll
        Default location: C:\Program Files (x86)\CA\SC\CAPKI\Windows\x86\32\lib
      • On UNIX: libccme_ecdrbg.so
        Default location: <install-location>/CAPKI/ <OSNAME>/<Architecture>/<32 or 64 based on bitness>/lib
        Ex: /home/fssuser/ca/webagent/CAPKI/Linux/amd64/64/lib/libccme_ecdrbg.so
    2. Add the following line in java.security file in <java-install-location>/jre/lib/security
      • com.rsa.crypto.default.random=HMACDRBG128
                      

Note: Web agents don't use any java and as a result it is not required to edit the java.security file on web agent only installations. For all other installations modify the java.security file that is being used by the product.