Gentoo: GLSA-201405-10: Rack: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in Rack. Please review the CVE identifiers referenced below for details.
Resolution
All Rack 1.4 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rack-1.4.5"
All Rack 1.3 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rack-1.3.10"
All Rack 1.2 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rack-1.2.8"
All Rack 1.1 users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rack-1.1.6"
References
[ 1 ] CVE-2012-6109 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-6109 [ 2 ] CVE-2013-0183 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0183 [ 3 ] CVE-2013-0184 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0184 [ 4 ] CVE-2013-0262 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0262 [ 5 ] CVE-2013-0263 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0263
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201405-10
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
![Dist Gentoo](/images/distros/dist-gentoo.png)
Synopsis
Multiple vulnerabilities have been found in Rack, the worst of which allow execution of arbitrary code.
Background
Rack is a modular Ruby web server interface.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-ruby/rack < 1.4.5 >= 1.4.5 *>= 1.3.10 *>= 1.2.8 *>= 1.1.6
Impact
===== A remote attacker could possibly execute arbitrary code with the privileges of the process, cause a Denial of Service condition, or obtain sensitive information.
Workaround
There is no known workaround at this time.