DL::dlopen could open a library with tainted library name even if $SAFE > 0. This vulnerability affects Ruby versions 1.8, 1.9, 2.1, 2.2. Upstream patch: https://github.com/ruby/ruby/commit/4600cf725a86ce31266153647ae5aa1197b1215b Additional information and CVE assignment: http://seclists.org/oss-sec/2015/q3/222
Created ruby tracking bugs for this issue: Affects: fedora-all [bug 1248937]
(In reply to Adam Mariš from comment #0) > DL::dlopen could open a library with tainted library name even if $SAFE > 0. > This vulnerability affects Ruby versions 1.8, 1.9, 2.1, 2.2. This is hardly true, since DL was removed from Ruby 2.2: https://github.com/ruby/ruby/commit/07308c4d30b8c5260e5366c8eed2abf054d86fe7
First of all, why is this CVE(-2009-5147, note "2009") reported now? The above oss-sec report says that this is already fixed in 1.9.1-p129.
Hello! This bug is only being reported now because the CVE was assigned only two days ago. Because the flaw was patched in 2009, it got a CVE from year 2009. As Vit noted above, this probably does not affect Ruby 2.2 but we still have to look into all other versions to see if they were patched.
This flaw has been re-introduced in Fiddle: "There is an unsafe tainted string vulnerability in Fiddle and DL. This issue was originally reported and fixed with CVE-2009-5147 in DL, but reappeared after DL was reimplemented using Fiddle and libffi. And, about DL, CVE-2009-5147 was fixed at Ruby 1.9.1, but not fixed at other branches, then rubies which bundled DL except Ruby 1.9.1 are still vulnerable." https://www.ruby-lang.org/en/news/2015/12/16/unsafe-tainted-string-usage-in-fiddle-and-dl-cve-2015-7551/
ruby-2.2.4-47.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
ruby-2.2.4-47.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 6 Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS Via RHSA-2018:0583 https://access.redhat.com/errata/RHSA-2018:0583