Bug 1153826

Summary: Disable SSLv3 in Satellite's httpd configuration (CVE-2014-3566)
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: SecurityAssignee: Tomer Brisker <tbrisker>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: abelopez, bbuckingham, bkearney, howey.vernon, mmccune, sthirugn, tbrisker
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:42:21 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1153811    

Description Mike McCune 2014-10-16 21:54:54 UTC
We need to disable SSLv3 support in the main ssl.conf file shipped and configured with Satellite 6.

More details to follow.

Comment 1 RHEL Program Management 2014-10-16 22:02:58 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 7 Tomer Brisker 2016-06-27 12:15:34 UTC
*** Bug 1305779 has been marked as a duplicate of this bug. ***

Comment 8 Tomer Brisker 2016-06-27 12:34:57 UTC
Satellite 6.2 will ship with puppetlabs-apache module version 1.8.1 in the installer which already disables SSLv3 by default: https://github.com/puppetlabs/puppetlabs-apache/blob/1.8.1/manifests/mod/ssl.pp#L8

Moving to ON_QA for verification.

Comment 10 Jitendra Yejare 2016-07-14 13:20:55 UTC
Verified !

@ Sat 6.2 Snap 19.1 GA

The SSLv3 is disabled in the httpd's ssl.conf

RHEL 7:
#cat /etc/httpd/conf.modules.d/ssl.conf | grep v3
  SSLProtocol all -SSLv2 -SSLv3

RHEL 6:
#cat /etc/httpd/conf.d/ssl.conf | grep v3
  SSLProtocol all -SSLv2 -SSLv3


So moving this bz to verified state.

Comment 11 Bryan Kearney 2016-07-27 11:42:21 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://access.redhat.com/errata/RHBA-2016:1501