"it was found that original upstream 1.8.x ruby patch for CVE-2011-1005 issue was not complete, when the NameError#to_s() method was used on / with Ruby objects (the test logic in 'test_to_s_taintness_propagation' test from [1] was actually reversed {Hint: Compare the test for Ruby Object cases in both [1] and [2]}, so the test returned success also on still vulnerable instances)."
Thanks for reporting, Hans.
dev-lang/ruby-1.9.3_p286 with a fix for this is now in the tree.
(In reply to comment #2) > dev-lang/ruby-1.9.3_p286 with a fix for this is now in the tree. What about the 1.8 slot? It looks like dev-lang/ruby-1.8.7_p370 is still affected.
Ah, you are right. Due to the poor wording of the original oss-security email I never realized 1.8 was affected as well. I see upstream has release p371, so we should get that in the tree as well.
dev-lang/ruby-1.8.7_p371 is now also in the tree.
Arches, please test and mark stable: =dev-lang/ruby-1.8.7_p371 Target KEYWORDS: "alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd"
amd64 stable
x86 stable
Stable for HPPA.
ppc done
sh stable
arm stable
ppc64 stable
alpha stable
ia64 stable
sparc stable
s390 stable
Added to existing GLSA draft.
CVE-2012-4481 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-4481): The safe-level feature in Ruby 1.8.7 allows context-dependent attackers to modify strings via the NameError#to_s method when operating on Ruby objects. NOTE: this issue is due to an incomplete fix for CVE-2011-1005.
This issue was resolved and addressed in GLSA 201412-27 at http://security.gentoo.org/glsa/glsa-201412-27.xml by GLSA coordinator Sean Amoss (ackle).