More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2294728 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
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=2294728,2294729 # 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 looked at the details of the four vulnerability reports in bug 2294728 and commented there. From Fedora point of view, all of those issues have been fixed upstream at 2.4.0 release or earlier. So Fedora had the fixes since 2022 when 2.4.0 was built in Fedora 36. So my conclusion is that Fedora is not vulnerable and I propose to close this bugzilla as NOTABUG. Please oppose loudly if you disagree.
Closing as NOTABUG with the explanation above.