More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2217798 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=2217798,2217806 # 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
According to common IT media and the people who found this CVE, the CVSS score is 9.8, i.e., very high. It would be important to get this fixed. @QA: Since there is no news from the assignee, would it be possible to get someone else to jump in? The new hotness already tried a scratch build, see bug #2182090.
(In reply to Christian Stadelmann from comment #2) > According to common IT media and the people who found this CVE, the CVSS > score is 9.8, i.e., very high. It would be important to get this fixed. > > @QA: Since there is no news from the assignee, would it be possible to get > someone else to jump in? > > The new hotness already tried a scratch build, see bug #2182090. That is the scratch build for 10.01.2, and the security bug claimed the bug to be present through that version. Apparantly that is wrong. I have commit rights for gs@fed but do not consider myself a maintainer, so I refrain from from version updates. But upstream has a backport for 10.01.1 so I'll check whether it's just a backport of the fix, or also of the fix to the fix ... This would be good for rawhide+f38. F37 is at gs 9.56, though. 9.55->9.56 was not exactly smooth, and bumping F37 to 10.01.1 would quite something I'm afraid.
OK, checked. We have 10.01.0 only in Fedora ... But 10.01.2 is purely a bugfix release, containing a fix for this CVE (and a fix for the fix) and some other bugfixes. So I'll go with this one. PR upcoming.
FEDORA-2023-b240ebd9aa has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b240ebd9aa
FEDORA-2023-d8a1c3e5e2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8a1c3e5e2
FEDORA-2023-d8a1c3e5e2 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d8a1c3e5e2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8a1c3e5e2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-d8a1c3e5e2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-b240ebd9aa has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
Thank you very very much, Michael J Gruber!