This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of epel-all. 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: http://fedoraproject.org/wiki/Security/TrackingBugs 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) type=security # low, medium, high, urgent (required) severity=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1699732,1699734 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11072 was disputed by a lighttpd developer (me), as the CVE was grossly written and poorly scoped. From the CVE: "NOTE: The developer states "The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf). Certain input will trigger an abort() in lighttpd when that feature is enabled. lighttpd detects the underflow or realloc() will fail (in both 32-bit and 64-bit executables), also detected in lighttpd. Either triggers an explicit abort() by lighttpd. This is not exploitable beyond triggering the explicit abort() with subsequent application exit." If RedHat/Fedora packages of lighttpd 1.4.50 - lighttpd 1.4.53 did not explicitly enable server.http-parseopts option "url-path-2f-decode" => "enable" in lighttpd.conf, then the CVE does not apply and this issue can be closed. Reference: https://redmine.lighttpd.net/issues/2945 The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf) with: server.http-parseopts = ( "url-path-2f-decode" => "enable" ) and can be disabled in the config file (or commented out) with: server.http-parseopts = ( "url-path-2f-decode" => "disable" ) losing only the functionality of that feature. The bug is fixed in lighttpd 1.4.54, and server.http-parseopts option "url-path-2f-decode" => "enable" becomes enabled by default in lighttpd 1.4.54, so please do not explicitly disable this feature in RedHat/Fedora packages from lighttpd 1.4.54 onwards.