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=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2120642,2120787 # 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
We're waiting for an upstream release that'll fix this issue. If someone would like it fixed sooner, let us know.
Hi Juneau, does product security need to own the Priority field for Fedora CVEs? We'd like to use it for bug triage in our team. We set it to low as we're not planning to actively backport the fix, but we're going to fix with a rebase.
(In reply to Tomas Orsava from comment #3) > Hi Juneau, > does product security need to own the Priority field for Fedora CVEs? We'd > like to use it for bug triage in our team. We set it to low as we're not > planning to actively backport the fix, but we're going to fix with a rebase. This bug marked as Moderate from Prod Sec side, But for fedora we are not own anything, the open community (maintainer) will decide if they fix or not or how they would like to fix.
(In reply to Sandipan Roy from comment #5) > (In reply to Tomas Orsava from comment #3) > > Hi Juneau, > > does product security need to own the Priority field for Fedora CVEs? We'd > > like to use it for bug triage in our team. We set it to low as we're not > > planning to actively backport the fix, but we're going to fix with a rebase. > > This bug marked as Moderate from Prod Sec side, But for fedora we are not > own anything, the open community (maintainer) will decide if they fix or not > or how they would like to fix. Exactly, our team, Python-maint, is the community maintainer of this package. And for us this is a low priority issue, because we'll fix it with a rebase when the fix is released upstream. So we set the Priority to low to indicate that, and to properly categorise it for our triage meetings. Let me try setting it again. Do you see any reason why ProdSec would need to overwrite our setting of the Priority of this BZ?
I don't know exactly, but IMO the main bug was marked as moderate so our auto tooling setting priority as moderate.
I've retired pypy3.7 on F37+. There will likely be no upstream fix. Once fixed in pypy3.8 we can backport it to Fedora 35 and 36. https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/755PXJKDEJAX3SN76B6ORRT4UJQ67IRX/
pypy3.7 is retired in f37+ so the fixes will be backported to f3[56] only
FEDORA-2022-01d5789c08 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-01d5789c08
FEDORA-2022-2173709172 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2173709172
FEDORA-2022-2173709172 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-2173709172` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2173709172 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-01d5789c08 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-01d5789c08` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-01d5789c08 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-2173709172 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-01d5789c08 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.