This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug. This will ensure that all associated bugs get updated
when new packages are pushed to stable.
# bugfix, security, enhancement, newpackage (required)
# testing, stable
# Bug numbers: 1234,9876
# Description of your update
notes=Security fix for [PUT CVEs HERE]
# Enable request automation based on the stable/unstable karma thresholds
# Automatically close bugs when this marked as stable
# Suggest that users restart after update
Additionally, you may opt to use the bodhi web interface to submit updates:
This appears to be fixed, and has been for a while?
In Fedora yeah, but not in epel7/6.
I don't use this package anymore, so I am going to let the primary admin take care of this...
Sorry, rephrase: the CVE fix is referenced in the 3.1.4-1 RPM changelog, the changelog in the source, and the code. So it appears to already be fixed (for epel7, at least. Did not check 6.)
Supervisor version at EPEL 6 is 2.1. I understand it's still affected by the CVE because it's a version under 3.0.1. I see two options: updating to 3.0.1 (but I think there are some braking changes), or trying to backport the bugfix to 2.1. I'll analyze this last option.
I've just read at supervisord's project:
This vulnerability has existed in all versions of Supervisor since 3.0a1 (released in 2007).
So there is no problem in EPEL 6. Closing this ticket...