This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of epel-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 EPEL. 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=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2007725,2007727 # 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
@Almeida - please let us know incase fedora epel based chromium browser is effected by that , we have a lot of red hat Linux server and Workstation where chromium browser is installed is there any remote code execution caught on red hat Linux servers anywhere ? in case the answer to the question is yes then when are we expecting updated package to be released by Fedora epel.? what is the severity of this vulnerability ?
(In reply to Surya Mishra from comment #2) > @Almeida - please let us know incase fedora epel based chromium browser is > effected by that , we have a lot of red hat Linux server and Workstation > where chromium browser is installed is there any remote code execution > caught on red hat Linux servers anywhere ? Chromium shipped in EPEL repositories are affected by this issue. > in case the answer to the question is yes then when are we expecting updated > package to be released by Fedora epel.? It should be updated soon, please use the flaw bug[1] and this tracker bug for updates. [1]. https://bugzilla.redhat.com/show_bug.cgi?id=2007725 > what is the severity of this vulnerability ? It's important.
EPEL 8 build is in progress (assuming nothing else broke in the update to 94): https://koji.fedoraproject.org/koji/buildinfo?buildID=1837850 It is noteworthy that Chromium is no longer being updated for EPEL7 (it is simply too old to build it for that target anymore), so if you have any Chromium installs on EL7, I strongly recommend that you either update them to EL8 or uninstall Chromium entirely.
FEDORA-EPEL-2021-a50497600b has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a50497600b
FEDORA-EPEL-2021-a50497600b has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a50497600b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2021-a50497600b has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.