More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2292836 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=medium # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2292836,2292841 # 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
Hi Patrick, I am not sure why this bug was filed for wget2, this is a new and different component than wget. The fix and the message from Upstream clearly state that the problem is in wget-1.x, not wget2. The same goes for wget2 in epel. Regards, Michal Ruprich
Hi Michal, this tracker should not have been created as this issue only affects wget (and not wget2). Closing this bug as not a bug.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days