Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1238324 - (CVE-2015-3277) CVE-2015-3277 mod_nss: incorrect multi-keyword mode cipherstring parsing
CVE-2015-3277 mod_nss: incorrect multi-keyword mode cipherstring parsing
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20150715,repor...
: Security
Depends On: 1243518 1253570
Blocks: 1210268 1238330
  Show dependency treegraph
 
Reported: 2015-07-01 11:26 EDT by Vasyl Kaigorodov
Modified: 2015-12-03 11:03 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-01 01:39:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vasyl Kaigorodov 2015-07-01 11:26:27 EDT
It was reported that mod_nss is vulnerable to the issue similar to CVE-2015-3276, where incorrect parsing of multi-keyword cipherstring can lead to an unexpected ciphers list advertising.

Acknowledgements:

Red Hat would like to thank Martin Poole of Software Maintenance Engineering group for reporting this issue.
Comment 2 Huzaifa S. Sidhpurwala 2015-08-14 03:02:29 EDT
The vulnerable code was added to mod_nss via the following commit:

https://git.fedorahosted.org/cgit/mod_nss.git/commit/?id=2d1650900f4d47dc43400d826c0f7e1a7c5229b8

And it was released as mod_nss-1.10.11

Therefore this does not affect the version of mod_nss package shipped with Red Hat Enterprise Linux 5, 6 and 7.
Comment 3 Huzaifa S. Sidhpurwala 2015-08-14 03:05:20 EDT
Statement:

This issue did not affect the versions of mod_nss as shipped with Red Hat Enterprise Linux 5, 6 and 7.

Note You need to log in before you can comment on or make changes to this bug.