BSAFE explained

BSAFE
Released:1996
Developer:Dell, formerly RSA Security
Programming Language:C, assembly, Java
Genre:Cryptography library, Commercial software
License:Proprietary
Operating System:BSD, Linux, macOS, Microsoft Windows, Android, iOS, AIX, Solaris

Dell BSAFE, formerly known as RSA BSAFE, is a FIPS 140-2 validated cryptography library, available in both C and Java. BSAFE was initially created by RSA Security, which was purchased by EMC and then, in turn, by Dell. When Dell sold the RSA business to Symphony Technology Group in 2020, Dell elected to retain the BSAFE product line.[1] [2] BSAFE was one of the most common encryption toolkits before the RSA patent expired in September 2000. It also contained implementations of the RCx ciphers, with the most common one being RC4. From 2004 to 2013 the default random number generator in the library was a NIST-approved RNG standard, widely known to be insecure from at least 2006, containing a kleptographic backdoor from the American National Security Agency (NSA), as part of its secret Bullrun program.[3] In 2013 Reuters revealed that RSA had received a payment of $10 million to set the compromised algorithm as the default option.[3] The RNG standard was subsequently withdrawn in 2014, and the RNG removed from BSAFE beginning in 2015.

Cryptography backdoors

Dual_EC_DRBG random number generator

From 2004 to 2013, the default cryptographically secure pseudorandom number generator (CSPRNG) in BSAFE was Dual_EC_DRBG, which contained an alleged backdoor from NSA, in addition to being a biased and slow CSPRNG.[4] The cryptographic community had been aware that Dual_EC_DRBG was a very poor CSPRNG since shortly after the specification was posted in 2005, and by 2007 it had become apparent that the CSPRNG seemed to be designed to contain a hidden backdoor for NSA, usable only by NSA via a secret key.[5] In 2007, Bruce Schneier described the backdoor as "too obvious to trick anyone to use it." The backdoor was confirmed in the Snowden leaks in 2013, and it was insinuated that NSA had paid RSA Security US$10 million to use Dual_EC_DRBG by default in 2004, though RSA Security denied that they knew about the backdoor in 2004. The Reuters article which revealed the secret $10 million contract to use Dual_EC_DRBG described the deal as "handled by business leaders rather than pure technologists". RSA Security has largely declined to explain their choice to continue using Dual_EC_DRBG even after the defects and potential backdoor were discovered in 2006 and 2007, and has denied knowingly inserting the backdoor.[6]

As a cryptographically secure random number generator is often the basis of cryptography, much data encrypted with BSAFE was not secure against NSA. Specifically it has been shown that the backdoor makes SSL/TLS completely breakable by the party having the private key to the backdoor (i.e. NSA). Since the US government and US companies have also used the vulnerable BSAFE, NSA can potentially have made US data less safe, if NSA's secret key to the backdoor had been stolen. It is also possible to derive the secret key by solving a single instance of the algorithm's elliptic curve problem (breaking an instance of elliptic curve cryptography is considered unlikely with current computers and algorithms, but a breakthrough may occur).

In June 2013, Edward Snowden began leaking NSA documents. In November 2013, RSA switched the default to HMAC DRBG with SHA-256 as the default option. The following month, Reuters published the report based on the Snowden leaks stating that RSA had received a payment of $10 million to set Dual_EC_DRBG as the default.

With subsequent releases of Crypto-C Micro Edition 4.1.2 (April 2016), Micro Edition Suite 4.1.5 (April 2016) and Crypto-J 6.2 (March 2015), Dual_EC_DRBG was removed entirely.

Extended Random TLS extension

"Extended Random" was a proposed extension for the Transport Layer Security (TLS) protocol, submitted for standardization to IETF by an NSA employee,[7] although it never became a standard. The extension would otherwise be harmless, but together with the Dual_EC_DRBG, it would make it easier to take advantage of the backdoor.[8] [9]

The extension was previously not known to be enabled in any implementations, but in December 2017, it was found enabled on some Canon printer models, which use the RSA BSAFE library, because the extension number conflicted a part of TLS version 1.3.

Varieties

Product suite support status

On November 25, 2015, RSA announced End of Life (EOL) dates for BSAFE.[17] The End of Primary Support (EOPS) was to be reached on January 31, 2017, and the End of Extended Support (EOXS) was originally set to be January 31, 2019. That date was later further extended by RSA for some versions until January 31, 2022.[18] During Extended Support, even though the support policy stated that only the most severe problems would be patched, new versions were released containing bugfixes, security fixes and new algorithms.[19]

On December 12, 2020, Dell announced the reversal of RSA's past decision, allowing BSAFE product support beyond January 2022 as well as the possibility to soon acquire new licenses. Dell also announced it was rebranding the toolkits to Dell BSAFE.[20]

External links

Notes and References

  1. Web site: BSAFE support and billing update Dell US. 2021-07-26. www.dell.com. 2021-07-26. https://web.archive.org/web/20210726191644/https://www.dell.com/support/kbdoc/en-us/000125778/bsafe-support-and-billing-update. live.
  2. News: RSA Emerges as Independent Company Following Completion of Acquisition by Symphony Technology Group . RSA . September 1, 2020 . RSA . June 7, 2023 . September 4, 2020 . https://web.archive.org/web/20200904082109/https://www.rsa.com/en-us/company/news/rsa--emerges-as-independent-company . live .
  3. News: Exclusive: Secret contract tied NSA and security industry pioneer . December 20, 2013 . Reuters . May 11, 2021 . Menn, Joseph . San Francisco . September 24, 2015 . https://web.archive.org/web/20150924191918/http://www.reuters.com/article/2013/12/20/us-usa-security-rsa-idUSBRE9BJ1C220131220 . live .
  4. Web site: RSA warns developers not to use RSA products. A Few Thoughts on Cryptographic Engineering. September 20, 2013. Matthew Green. December 28, 2013. October 10, 2013. https://web.archive.org/web/20131010085457/http://blog.cryptographyengineering.com/2013/09/rsa-warns-developers-against-its-own.html. live.
  5. Web site: The Strange Story of Dual_EC_DRBG. Bruce Schneier. 2013-12-28. 2019-04-23. https://web.archive.org/web/20190423212823/https://www.schneier.com/blog/archives/2007/11/the_strange_sto.html. live.
  6. Web site: We don’t enable backdoors in our crypto products, RSA tells customers. Ars Technica. 2017-06-14. 2014-10-12. https://web.archive.org/web/20141012130722/http://arstechnica.com/security/2013/09/we-dont-enable-backdoors-in-our-crypto-products-rsa-tells-customers/. live.
  7. draft-rescorla-tls-extended-random-02 . Extended Random Values for TLS . Eric . Rescorla . Margaret . Salter . 2 March 2009 . IETF draft standard . en . 2023-09-28 . 19 December 2017 . https://web.archive.org/web/20171219203836/https://tools.ietf.org/html/draft-rescorla-tls-extended-random-02 . live.
  8. News: Exclusive: NSA infiltrated RSA security more deeply than thought - stu. Menn. Joseph. 31 March 2014. Reuters. en-GB. 28 December 2017. 29 December 2017. https://web.archive.org/web/20171229112257/https://uk.reuters.com/article/us-usa-security-nsa-rsa/exclusive-nsa-infiltrated-rsa-security-more-deeply-than-thought-study-idUKBREA2U0TY20140331. live.
  9. News: The strange story of "Extended Random". Green. Matthew. 19 December 2017. Cryptographic Engineering blog. en-US. 28 December 2017. 29 December 2017. https://web.archive.org/web/20171229020021/https://blog.cryptographyengineering.com/2017/12/19/the-strange-story-of-extended-random/. live.
  10. Web site: RSA licenses Baltimore Technologies J/CRYPTO.
  11. Web site: RSA's BSafe toolkit spawns new Java version.
  12. Web site: Making Java Development JSafe. 2020-04-27. 2021-09-28. https://web.archive.org/web/20210928213114/https://vintageapple.org/byte/pdf/199801_Byte_Magazine_Vol_23-01_Next_Years_Top_Tech.pdf. live.
  13. News: February 20, 2002. RSA unveils three new products at its show. IT World.
  14. Book: Web Security, Privacy & Commerce . Simson Garfinkel, Gene Spafford . O'Reilly . 2002 . 114 . 0596000456 .
  15. Book: OpenSSL Cookbook: A Guide to the Most Frequently Used OpenSSL Features and Commands . Ivan Ristic . 2013 . 9781907117053 . Qualys . 1 .
  16. Web site: Securing IT Resources with Digital Certificates and LDAP. 2020-04-27. 2020-07-31. https://web.archive.org/web/20200731083811/https://www.educause.edu/ir/library/html/cnc9707/cnc9707.html. live.
  17. Web site: RSA announces End of Life (EOL) dates for RSA BSAFE . RSA . November 25, 2015 . RSA . October 3, 2018 . October 3, 2018 . https://web.archive.org/web/20181003181713/https://community.rsa.com/docs/DOC-59312 . live .
  18. Web site: RSA announces support extension for some of the BSAFE® product suite . RSA . June 20, 2018 . RSA . October 3, 2018 . October 3, 2018 . https://web.archive.org/web/20181003181732/https://community.rsa.com/docs/DOC-93720 . live .
  19. Web site: RSA announces the release of RSA BSAFE® Micro Edition Suite 4.4 . RSA . September 11, 2019 . RSA . September 11, 2019 . September 23, 2019 . https://web.archive.org/web/20190923221524/https://community.rsa.com/docs/DOC-107002 . live .
  20. News: Dell BSAFE products remain supported beyond January 2022, reversing RSA's past decision to end-of-life BSAFE toolkits. . Dell . December 12, 2020. Dell.

This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "BSAFE".

Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.