Fedora Account System
Red Hat Associate
Red Hat Customer
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 # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1561296,1561298 # 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
Merged rawhide: https://src.fedoraproject.org/rpms/cups/pull-request/1
I'll rebase cups to 2.2.7 in rawhide, accept Pavel's pull request for F28 and backport it to f27 and f28.
(In reply to Zdenek Dohnal from comment #3) > and f28. I meant f26 of course.
Ah, I see - all branches were solved - thank you Pavel!
Actually, as #1561296 says, this issue is fixed in 2.2.6, which means it is fixed for f28 and f29 by rebase done 2017-11-03. So backporting was needed only for f26 and f27. I'll revert changes for f28 and f29 because of duplicating. But there are two other issues connected to this issue, which aren't in cups-2.2.6 and don't fix actual CVE, but IMO it would be good to have it fixed too. To sum it up: 1) for f29 rebase to cups-2.2.7 and backport one fix from cups-2.3b4, revert duplicate CVE fix 2) for f28 backport fix from 2.2.7 and from 2.3b4, revert duplicate CVE fix 3) for f26 and f27 backport fixes from 2.2.7 and 2.3b4, keep backported CVE fix
To clarify it again, security bodhi update will contain only cups for f26 and f27, where issue wasn't fixed.
cups-2.2.4-9.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-99f551e4ff
cups-2.2.2-9.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ec5f10e626
cups-2.2.2-9.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ec5f10e626
cups-2.2.4-9.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-99f551e4ff
cups-2.2.4-9.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
cups-2.2.2-9.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.