Description of problem: The default value SSL_CBC_RANDOM_IV SSL is currently turned off and users must turn it on to activate the fix for CVE-2011-3389 as we do on Rawhide. It should be other way around. The defense against the SSL 3.0 and TLS 1.0 CBC chosen plaintext attack demonstrated by Rizzo and Duong (CVE-2011-3389) [1] has been in implemented in nss since nss-3.13 and in Fedora since nss-3.13.1. NSS queries the SSL_CBC_RANDOM_IV SSL environment variable to activate the fix. For Fedora stable branches until now we have overriden the NSS upstream default value of 1 and set it to 0 in order to avoid breakage for users and client applications that needed to connect to still unpatched servers. The user (user or application) had to turn explicetly the variable on to get the extra security. This a propoasl to keep the more secure option as the default. If, for reasons of compatibility with remaining unpatched servers or applications, the user can opt out by setting SSL_CBC_RANDOM_IV SSL to 0. [1] http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3389 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This is very is easy fix, a one-line change to disable application of the patch that overrides the upstream default settings. We should eventually we remove the patch altogther
As posted to devel-announce.org: ----- Original Message ----- From: "Eric H. Christensen" <sparks> To: devel-announce.org Sent: Wednesday, October 16, 2013 1:33:06 PM Subject: BEAST to be patched in NSS -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 FESCo met today to address the NSS BEAST patch that left all software using NSS vulnerable to the BEAST[0] vulnerability. The decision was made to implement the patch that fixes this vulnerablity in F19 and F20. There are some programs that may have difficulties with this fix. While the fix will go in as soon as possible the change in F19 will not be applied until some testing has been completed. Information on this fix is in Bugzilla[1]. If your package depends on NSS you should definitely test this patch before it goes live in order to determine if it breaks functionality (information on the BZ ticket on how to disable the fix if needed). [0] https://en.wikipedia.org/wiki/BEAST_%28computer_security%29#BEAST_attack [1] https://bugzilla.mozilla.org/show_bug.cgi?id=665814 - -- Eric
Created attachment 813536 [details] nss.spec changes to preserve upstream default for BEAST -- in patch form
nss-3.15.2-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nss-3.15.2-2.fc20
Package nss-3.15.2-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nss-3.15.2-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19396/nss-3.15.2-2.fc20 then log in and leave karma (feedback).
nss-3.15.2-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.