Bug 862614 - (CVE-2012-4466) CVE-2012-4466 ruby: safe level bypass via name_err_mesg_to_str()
CVE-2012-4466 ruby: safe level bypass via name_err_mesg_to_str()
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
: 862906 (view as bug list)
Depends On: 839530 862907 863315 904021
Blocks: 767033 862631
  Show dependency treegraph
Reported: 2012-10-03 07:47 EDT by Jan Lieskovsky
Modified: 2015-07-31 02:54 EDT (History)
10 users (show)

See Also:
Fixed In Version: ruby 1.9.3p286, ruby 1.8.7p371
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-09-05 20:49:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2012-10-03 07:47:46 EDT
Originally, Common Vulnerabilities and Exposures assigned an identifier CVE-2011-1005 to the following vulnerability:

The safe-level feature in Ruby 1.8.6 through 1.8.6-420, 1.8.7 through 1.8.7-330, and 1.8.8dev allows context-dependent attackers to modify strings via the Exception#to_s method, as demonstrated by changing an intended pathname.

Later it was reported:
[1] http://www.openwall.com/lists/oss-security/2012/10/02/4

that the Ruby name_err_mesg_to_str() method is vulnerable to the similar flaw.

Relevant upstream patch:
[2] http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=37068
Comment 2 Vincent Danen 2012-10-03 16:57:38 EDT
*** Bug 862906 has been marked as a duplicate of this bug. ***
Comment 3 Vincent Danen 2012-10-03 17:03:24 EDT
Created ruby tracking bugs for this issue

Affects: fedora-all [bug 862907]
Comment 9 errata-xmlrpc 2013-02-28 14:08:18 EST
This issue has been addressed in following products:

  RHEL 6 Version of OpenShift Enterprise

Via RHSA-2013:0582 https://rhn.redhat.com/errata/RHSA-2013-0582.html

Note You need to log in before you can comment on or make changes to this bug.