More information about these security flaws is available in the following bugs: http://bugzilla.redhat.com/show_bug.cgi?id=2172927 http://bugzilla.redhat.com/show_bug.cgi?id=2172926 http://bugzilla.redhat.com/show_bug.cgi?id=2172930 http://bugzilla.redhat.com/show_bug.cgi?id=2172931 http://bugzilla.redhat.com/show_bug.cgi?id=2172928 http://bugzilla.redhat.com/show_bug.cgi?id=2172932 http://bugzilla.redhat.com/show_bug.cgi?id=2172929 http://bugzilla.redhat.com/show_bug.cgi?id=2172933 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=urgent # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2172926,2172927,2172928,2172929,2172930,2172931,2172932,2172933,2172934 # 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
FEDORA-2023-523a24d90a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-523a24d90a
FEDORA-2023-523a24d90a has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-523a24d90a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-06e40bcae5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-06e40bcae5
FEDORA-2023-1cf9c4477b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1cf9c4477b
FEDORA-EPEL-2023-7b23e5a4b3 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7b23e5a4b3
FEDORA-2023-06e40bcae5 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-06e40bcae5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-7b23e5a4b3 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7b23e5a4b3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-1cf9c4477b has been pushed to the Fedora 37 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-1cf9c4477b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1cf9c4477b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-523a24d90a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-1cf9c4477b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-a5e10b188a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2023-7b23e5a4b3 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.