RHSA-2014:0151: Low: wget security and bug fix update
The wget package provides the GNU Wget file retrieval utility for HTTP,HTTPS, and FTP protocols. Wget provides various useful features, such asthe ability to work in the background while the user is logged out,recursive retrieval of directories, file name wildcard matching or updatingfiles in dependency on file timestamp comparison.It was discovered that wget used a file name provided by the server whensaving a downloaded file. This could cause wget to create a file with adifferent name than expected, possibly allowing the server to executearbitrary code on the client. (CVE-2010-2252)Note: With this update, wget always uses the last component of the originalURL as the name for the downloaded file. Previous behavior of using theserver provided name or the last component of the redirected URL whencreating files can be re-enabled by using the '--trust-server-names'command line option, or by setting 'trustservernames=on' in the wgetstart-up file.This update also fixes the following bugs: Prior to this update, the wget package did not recognize HTTPS SSL certificates with alternative names (subjectAltName) specified in thecertificate as valid. As a consequence, running the wget command failedwith a certificate error. This update fixes wget to recognize suchcertificates as valid. (BZ#1060113)All users of wget are advised to upgrade to this updated package, whichcontain backported patches to correct these issues.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2014:0151?
The severity of RHSA-2014:0151 is classified as low.
How do I fix RHSA-2014:0151?
To fix RHSA-2014:0151, update the wget package to version 1.12-1.11.el6_5.
What versions of wget are affected by RHSA-2014:0151?
The affected versions of wget are any version prior to 1.12-1.11.el6_5.
Does RHSA-2014:0151 affect wget-debuginfo packages?
Yes, RHSA-2014:0151 affects wget-debuginfo packages that are prior to version 1.12-1.11.el6_5.
Is it important to address RHSA-2014:0151 promptly?
Yes, it is important to address RHSA-2014:0151 promptly to reduce potential security risks.