Randy Barlow of Red Hat reports: In working on another security issue in this same script, I noticed that Pulp's pulp-qpid-ssl-cfg script uses bash's $RANDOM in unsafe ways. One of them is already being fixed as part of another CVE (the TMP directory is unsafe, CVE-2016-3696), but the other two uses are: 0) The default NSS DB password is a single value from $RANDOM, limiting it to the strings from 0 to 32768: https://github.com/pulp/pulp/blob/pulp-2.8.2-1/server/bin/pulp-qpid-ssl-cfg#L25 [Open URL] 1) The certutil -z flag receives a "noise file". The script uses $RANDOM to populate a file with numbers to generate this file: https://github.com/pulp/pulp/blob/pulp-2.8.2-1/server/bin/pulp-qpid-ssl-cfg#L97-L105 [Open URL] Since $RANDOM is used in this way, the seed file ends up having low diversity since only 11 possibly bytes appear in the file: 0-9 and newline. I know that I can use pwgen to fix #0, but I'm not sure we want to depend on pwgen. One possibility is to avoid having a default password and force the user to provide one. Do you have a suggestion on a good way to make a password? For #1 I will just grab 8 kB from /dev/urandom and call it a day.
Acknowledgments: Name: Randy Barlow (RedHat)
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
pulp-2.8.6-1.fc24, pulp-docker-2.0.2-1.fc24, pulp-ostree-1.1.2-1.fc24, pulp-puppet-2.8.6-2.fc24, pulp-python-1.1.2-1.fc24, pulp-rpm-2.8.6-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
This issue has been addressed in the following products: Red Hat Satellite 6.3 for RHEL 7 Via RHSA-2018:0336 https://access.redhat.com/errata/RHSA-2018:0336