More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2254067 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=low # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2254067,2254069 # 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 39 and Rawhide already contain tar-1.35, where the upstream commit (https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4) was applied. Is there another reason why this bug was filled to Fedora?
(In reply to Lukas Javorsky from comment #2) > Fedora 39 and Rawhide already contain tar-1.35, where the upstream commit > (https://git.savannah.gnu.org/cgit/tar.git/commit/ > ?id=a339f05cd269013fa133d2f148d73f6f7d4247e4) was applied. > > Is there another reason why this bug was filled to Fedora? Apologies, not sure if I had just misread or had an older version when I had checked the version for f39. Closing this as notaffected.
(In reply to Lukas Javorsky from comment #2) > Fedora 39 and Rawhide already contain tar-1.35, where the upstream commit > (https://git.savannah.gnu.org/cgit/tar.git/commit/ > ?id=a339f05cd269013fa133d2f148d73f6f7d4247e4) was applied. > > Is there another reason why this bug was filled to Fedora? Hi, Fedora 38 ships tar-1.34 and seems affected by this issue. This tracker bug is for all supported versions of Fedora. Could you please check? Thank you!
Yes, it affects it, but we've decided to not fix this bug prior to Fedora version 39.
If you have some concerns or business justification, which will raise the priority of this CVE, please let us know, so we can reconsider the decision.