This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-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. 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=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1844929,1847481 # 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
I didn't check f31, but f32 looks like fixed. Apologies, feel free to CLOSE that tracker
Yes, updated packages of nghttp2 for Fedora were available 14 days before this tracker was created. Anyway, I do not understand why we have separate trackers for nodejs:10/nghttp2, nodejs:11/nghttp2, nodejs:12/nghttp2, nodejs:13/nghttp2, and nodejs:14/nghttp2. I thought there was only one nghttp2 package in Fedora. Could you please clarify it?
Hi Kamil, The manifest (database we use to keep track of components and modules within components) report these nodejs:*/nghttp2 as separate components After a quick check : the nodejs:14 module seems to currently have nghttp2-0:1.41.0-1.module_f32+9030+0a08c360.src , while nodejs:13 has nghttp2-0:1.40.0-2.module_f32+8199+88b63a05.src, so they look like based on different component (I used the following command to search that on f32 : `for x in nodejs:1{0,2,3,4}; do echo $x; dnf module info $x | grep "\bnghttp2" ; done`)
Thanks for the quick reply on this! It is definitely not me who takes care of the mentioned module builds. Stephen, any idea how I got assigned to these bugs for components that I had no idea they had ever existed?
(In reply to Kamil Dudka from comment #5) > Thanks for the quick reply on this! It is definitely not me who takes care > of the mentioned module builds. > > Stephen, any idea how I got assigned to these bugs for components that I had > no idea they had ever existed? Because it was filed against nghttp2, not against the modules? Reassigning.
Cedric, could you please update the manifest such that these bugs are filed for Product: Fedora Modules and Component: nodejs next time?
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.