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=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2081879,2082345 # 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
Can you eloborate how this CVE relates to byte-buddy package? To me it seems unrelated.
(In reply to Mikolaj Izdebski from comment #2) > Can you eloborate how this CVE relates to byte-buddy package? > To me it seems unrelated. Based on our manifests, byte-buddy transitively requires a vulnerable version of google-oauth-client.[1] [1] fedora-34 | byte-buddy-1.10.14-2.fc34 | (gradle-6.0.1/lib/plugins/google-oauth-client.0, maven)
I think I see the issue: byte-buddy source package in Fedora 34 contains the whole bundled binary distribution of gradle. This is removed during %prep and is not used at all during the build. Since Fedora 35 we switched from removing gradle in %prep to removing it even before uploading the archive to Fedora sources. byte-buddy packaged in Fedora 34 or any newer one does not use gradle. It just happened that the source package of byte-buddy in Fedora 34 contains gradle.
To recapitulate: byte-buddy in Fedora neither BuildRequires, nor Requires gradle. Can I close this bug?
(In reply to Marián Konček from comment #5) > To recapitulate: byte-buddy in Fedora neither BuildRequires, nor Requires > gradle. > > Can I close this bug? Yup, go ahead.