RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1228913 - Rebase to nss-3.19.1 for CVE-2015-4000 [RHEL-7.1]
Summary: Rebase to nss-3.19.1 for CVE-2015-4000 [RHEL-7.1]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss
Version: 7.1
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: 7.1
Assignee: Elio Maldonado Batiz
QA Contact: Hubert Kario
URL:
Whiteboard:
Depends On:
Blocks: CVE-2015-4000, LOGJAM
TreeView+ depends on / blocked
 
Reported: 2015-06-06 15:26 UTC by Elio Maldonado Batiz
Modified: 2015-11-19 12:27 UTC (History)
5 users (show)

Fixed In Version: nss-3.19.1-6.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
The nss and nss-util packages have been upgraded to upstream version 3.19.1, which provides a number of bug fixes and enhancements over the previous version. Notably, the update allows users to upgrade to Mozila Firefox 38 Extended Support Release and prevents attackers from exploiting the Logjam security vulnerability CVE-2015-4000.
Clone Of:
Environment:
Last Closed: 2015-11-19 12:27:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
all changes needed for nss rebase for rhel-7.1.z (25.40 KB, patch)
2015-06-06 17:57 UTC, Elio Maldonado Batiz 		no flags Details | Diff
all changes needed for nss rebase for rhel-7.1.z (28.10 KB, patch)
2015-06-08 21:30 UTC, Elio Maldonado Batiz 		no flags Details | Diff
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1138554 0 None None None Never
Red Hat Product Errata RHBA-2015:2121 0 normal SHIPPED_LIVE nss bug fix and enhancement update 2015-11-19 11:01:16 UTC

Description Elio Maldonado Batiz 2015-06-06 15:26:35 UTC 
nss-3.19.1 contains the fix for CVE-2015-4000 aka LOGJAM.
Comment 1 Elio Maldonado Batiz 2015-06-06 17:57:14 UTC 
Created attachment 1035693 [details]
all changes needed for nss rebase for rhel-7.1.z
Comment 5 Elio Maldonado Batiz 2015-06-08 14:14:39 UTC 
Comment on attachment 1035693 [details]
all changes needed for nss rebase for rhel-7.1.z

These are the changes:
1) .gitignore and source updated because of the rebase
2) expired-cert.patch removed as no lo longer needed
3) Patch91: nss-3.18.1-ca-2.3-to-2.4.patch removed, obsoleted
4) Patch95: expired-cert.patch removed, obsoleted
5) Patch96: syntaxfix.patch removed, obsoleted
6) Patch98: nss-revert-tls-version-defaults.patch to keep the TLS protocol versions that are enabled by default is no longer a straight reversal of an upstream patch as it was with 3.18.0 so the -R is not applicable.
7) iquote.patch updated as the there is a new public API
8) Notice at the top of nss.spec that %global required_softokn_build_version changed from -11 to -10 because we are temporarily backtracking the changes previously made to add support for sha384 tls cipher suites. They will come back one this rebase is completed.
Comment 9 Kai Engert (:kaie) (inactive account) 2015-06-08 16:48:27 UTC 
I think the most recently attached patch is insufficient. It doesn't include the change of magic numbers made to softokn by upstream. I understand we might not want to change softokn. In that case we should apply the patch from upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=1172128 on top of 3.19.1
Comment 10 Kai Engert (:kaie) (inactive account) 2015-06-08 17:02:23 UTC 
Also, the attached patch is broken.

checking file .gitignore
checking file expired-cert.patch
checking file iquote.patch
patch: **** malformed patch at line 48: @@ -1,326 +0,0 @@
Comment 11 Kai Engert (:kaie) (inactive account) 2015-06-08 17:53:28 UTC 
Sorry, my comment 10 was a false alarm.
I made a mistake when downloading the patch.

Patch applies on my local tree.

Nevertheless, my comment 9 still stands.

I'll continue the review of the patch.
Comment 12 Elio Maldonado Batiz 2015-06-08 21:30:49 UTC 
Created attachment 1036471 [details]
all changes needed for nss rebase for rhel-7.1.z

Completes the need changes as Kai pointed out on Comment 8, with the ssl-server-min-key-sizes.patch suitably modified so DH_MIN_P_BITS is 768.
Comment 13 Bob Relyea 2015-06-09 17:38:55 UTC 
upstream reverted their changes refered to in comment 9, so there is no need to pick up a new softoken.

bob
Comment 16 errata-xmlrpc 2015-11-19 12:27:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2121.html
Note You need to log in before you can comment on or make changes to this bug.