Skip to content

Commit

Permalink
Add release notes for the CVEs included with Pulp 2.8.4.
Browse files Browse the repository at this point in the history
re #1854
re #1858
  • Loading branch information
bowlofeggs authored and Randy Barlow committed May 23, 2016
1 parent 8156084 commit d86b111
Showing 1 changed file with 39 additions and 0 deletions.
39 changes: 39 additions & 0 deletions docs/user-guide/release-notes/2.8.x.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,45 @@ Pulp 2.8 Release Notes
======================


Pulp 2.8.4
==========

.. warning::

User action is required to address the CVEs associated with this upgrade! Read the upgrade
instructions below.

2.8.4 is a security and bugfix release.

Included in the list of :fixedbugs:`2.8.4` are two CVEs:

* `CVE-2016-3696 <https://pulp.plan.io/issues/1854>`_: Leakage of CA key in pulp-qpid-ssl-cfg
* `CVE-2016-3704 <https://pulp.plan.io/issues/1858>`_: Unsafe use of bash $RANDOM for NSS DB
password and seed


Upgrade instructions
--------------------

The CVEs require user interaction to remedy if you have been using qpid, and if you used
``pulp-qpid-ssl-cfg`` to generate the TLS keys. Rabbit users and users who generated their own keys
for qpidd are not affected by these CVEs. Begin by upgrading to Pulp 2.8.4 and running migrations::

$ sudo systemctl stop qpidd httpd pulp_workers pulp_resource_manager pulp_celerybeat goferd
$ sudo yum upgrade
$ sudo -u apache pulp-manage-db

Any qpidd CA, server and client certificate and key pairs that were generated with
``pulp-qpid-ssl-cfg`` are unsafe and should be replaced. After upgrading to 2.8.4 (as we did above),
you can use the script to replace the certificates and keys::

$ sudo pulp-qpid-ssl-cfg

Now we are ready to start the services again::

$ sudo systemctl start qpidd httpd pulp_workers pulp_resource_manager pulp_celerybeat goferd


Pulp 2.8.3
==========

Expand Down

0 comments on commit d86b111

Please sign in to comment.