Bug 919172

Summary: Rebase to nss-softokn 3.14.3 to fix the lucky-13 issue [6.5]
Product: Red Hat Enterprise Linux 6 Reporter: Elio Maldonado Batiz <emaldona>
Component: nss-softoknAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED ERRATA QA Contact: Hubert Kario <hkario>
Severity: medium Docs Contact:
Priority: high    
Version: 6.5CC: amarecek, eparis, hkario, kengert, ksrot, rrelyea, sforsber, thoger
Target Milestone: rcKeywords: Rebase, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: nss-softokn-3.14.3-1.el6 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
This advisory rebases the nss-softokn package 3.14.3 to address CVE-2013-1620 - Non-constant time CBC decoding results in padding oracle, aka Lucky Thirteen attack. Bug 822365
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 06:11:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 919174, 919180    
Bug Blocks: 918950, 927158    

Description Elio Maldonado Batiz 2013-03-07 18:53:05 UTC
Description of problem: Bug 918950 - [RFE][RHEL6] was entered to rebase to nss-3.14.3 to fix the lucky-13 issue. Since the fix encompases changes to the softoken/freebl code so we also need to rebase nss-softokn to the same version as nss.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 4 Kai Engert (:kaie) (inactive account) 2013-03-22 17:46:34 UTC
I guess this bug needs the blocker flag, because I see it in bug 919174 and bug 918950 ?

Comment 7 Eric Paris 2013-08-07 18:53:20 UTC
*** Bug 821440 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2013-11-21 06:11:58 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.