Ruby 1.9.3 before patchlevel 286 and 2.0 before revision r37068 allows context-dependent attackers to bypass safe-level restrictions and modify untainted strings via the (1) exc_to_s or (2) name_err_to_s API function, which marks the string as tainted, a different vulnerability than CVE-2012-4466. NOTE: this issue might exist because of a CVE-2011-1005 regression.

According to the versions of the ruby packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - Ruby 1.8.7 before patchlevel 371, 1.9.3 before     patchlevel 286, and 2.0 before revision r37068 allows     context-dependent attackers to bypass safe-level     restrictions and modify untainted strings via the     name_err_mesg_to_str API function, which marks the     string as tainted, a different vulnerability than     CVE-2011-1005.(CVE-2012-4466)

  - The REXML parser in Ruby 1.9.x before 1.9.3 patchlevel     551, 2.0.x before 2.0.0 patchlevel 598, and 2.1.x     before 2.1.5 allows remote attackers to cause a denial     of service (CPU and memory consumption) a crafted XML     document containing an empty string in an entity that     is used in a large number of nested entity references,     aka an XML Entity Expansion (XEE) attack. NOTE: this     vulnerability exists because of an incomplete fix for     CVE-2013-1821 and CVE-2014-8080.(CVE-2014-8090)

  - Algorithmic complexity vulnerability in     Gem::Version::VERSION_PATTERN in     lib/rubygems/version.rb in RubyGems before 1.8.23.1,     1.8.24 through 1.8.25, 2.0.x before 2.0.8, and 2.1.x     before 2.1.0, as used in Ruby 1.9.0 through 2.0.0p247,     allows remote attackers to cause a denial of service     (CPU consumption) via a crafted gem version that     triggers a large amount of backtracking in a regular     expression.(CVE-2013-4287)

  - The REXML parser in Ruby 1.9.x before 1.9.3-p550, 2.0.x     before 2.0.0-p594, and 2.1.x before 2.1.4 allows remote     attackers to cause a denial of service (memory     consumption) via a crafted XML document, aka an XML     Entity Expansion (XEE) attack.(CVE-2014-8080)

  - The OpenSSL::SSL.verify_certificate_identity function     in lib/openssl/ssl.rb in Ruby 1.8 before 1.8.7-p374,     1.9 before 1.9.3-p448, and 2.0 before 2.0.0-p247 does     not properly handle a '\\0' character in a domain name     in the Subject Alternative Name field of an X.509     certificate, which allows man-in-the-middle attackers     to spoof arbitrary SSL servers via a crafted     certificate issued by a legitimate Certification     Authority, a related issue to     CVE-2009-2408.(CVE-2013-4073)

  - The rb_get_path_check function in file.c in Ruby 1.9.3     before patchlevel 286 and Ruby 2.0.0 before r37163     allows context-dependent attackers to create files in     unexpected locations or with unexpected names via a NUL     byte in a file path.(CVE-2012-4522)

  - (1) DL and (2) Fiddle in Ruby 1.9 before 1.9.3     patchlevel 426, and 2.0 before 2.0.0 patchlevel 195, do     not perform taint checking for native functions, which     allows context-dependent attackers to bypass intended     $SAFE level restrictions.(CVE-2013-2065)

  - Algorithmic complexity vulnerability in     Gem::Version::ANCHORED_VERSION_PATTERN in     lib/rubygems/version.rb in RubyGems before 1.8.23.2,     1.8.24 through 1.8.26, 2.0.x before 2.0.10, and 2.1.x     before 2.1.5, as used in Ruby 1.9.0 through 2.0.0p247,     allows remote attackers to cause a denial of service     (CPU consumption) via a crafted gem version that     triggers a large amount of backtracking in a regular     expression. NOTE: this issue is due to an incomplete     fix for CVE-2013-4287.(CVE-2013-4363)

  - Ruby (aka CRuby) 1.9 before 1.9.3-p327 and 2.0 before     r37575 computes hash values without properly     restricting the ability to trigger hash collisions     predictably, which allows context-dependent attackers     to cause a denial of service (CPU consumption) via     crafted input to an application that maintains a hash     table, as demonstrated by a universal multicollision     attack against a variant of the MurmurHash2 algorithm,     a different vulnerability than     CVE-2011-4815.(CVE-2012-5371)

  - Off-by-one error in the encodes function in pack.c in     Ruby 1.9.3 and earlier, and 2.x through 2.1.2, when     using certain format string specifiers, allows     context-dependent attackers to cause a denial of     service (segmentation fault) via vectors that trigger a     stack-based buffer overflow.(CVE-2014-4975)

  - Heap-based buffer overflow in Ruby 1.8, 1.9 before     1.9.3-p484, 2.0 before 2.0.0-p353, 2.1 before 2.1.0     preview2, and trunk before revision 43780 allows     context-dependent attackers to cause a denial of     service (segmentation fault) and possibly execute     arbitrary code via a string that is converted to a     floating point value, as demonstrated using (1) the     to_f method or (2) JSON.parse.(CVE-2013-4164)

  - It was found that the methods from the Dir class did     not properly handle strings containing the NULL byte.
    An attacker, able to inject NULL bytes in a path, could     possibly trigger an unspecified behavior of the ruby     script.(CVE-2018-8780)

  - Ruby 1.9.3 before patchlevel 286 and 2.0 before     revision r37068 allows context-dependent attackers to     bypass safe-level restrictions and modify untainted     strings via the (1) exc_to_s or (2) name_err_to_s API     function, which marks the string as tainted, a     different vulnerability than CVE-2012-4466. NOTE: this     issue might exist because of a CVE-2011-1005     regression.(CVE-2012-4464)

  - An issue was discovered in the OpenSSL library in Ruby     before 2.3.8, 2.4.x before 2.4.5, 2.5.x before 2.5.2,     and 2.6.x before 2.6.0-preview3. When two     OpenSSL::X509::Name objects are compared using ==,     depending on the ordering, non-equal objects may return     true. When the first argument is one character longer     than the second, or the second argument contains a     character that is one less than a character in the same     position of the first argument, the result of == will     be true. This could be leveraged to create an     illegitimate certificate that may be accepted as     legitimate and then used in signing or encryption     operations.(CVE-2018-16395)

  - An issue was discovered in Ruby before 2.3.8, 2.4.x     before 2.4.5, 2.5.x before 2.5.2, and 2.6.x before     2.6.0-preview3. It does not taint strings that result     from unpacking tainted strings with some     formats.(CVE-2018-16396)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Red Hat OpenShift Enterprise 1.1.1 is now available.

The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

OpenShift Enterprise is a cloud computing Platform-as-a-Service (PaaS) solution from Red Hat, and is designed for on-premise or private cloud deployments.

Installing the updated packages and restarting the OpenShift services are the only requirements for this update. However, if you are updating your system to Red Hat Enterprise Linux 6.4 while applying OpenShift Enterprise 1.1.1 updates, it is recommended that you restart your system.

For further information about this release, refer to the OpenShift Enterprise 1.1.1 Technical Notes, available shortly from https://access.redhat.com/knowledge/docs/

This update also fixes the following security issues :

Multiple cross-site scripting (XSS) flaws were found in rubygem-actionpack. A remote attacker could use these flaws to conduct XSS attacks against users of an application using rubygem-actionpack.
(CVE-2012-3463, CVE-2012-3464, CVE-2012-3465)

It was found that certain methods did not sanitize file names before passing them to lower layer routines in Ruby. If a Ruby application created files with names based on untrusted input, it could result in the creation of files with different names than expected.
(CVE-2012-4522)

A denial of service flaw was found in the implementation of associative arrays (hashes) in Ruby. An attacker able to supply a large number of inputs to a Ruby application (such as HTTP POST request parameters sent to a web application) that are used as keys when inserting data into an array could trigger multiple hash function collisions, making array operations take an excessive amount of CPU time. To mitigate this issue, a new, more collision resistant algorithm has been used to reduce the chance of an attacker successfully causing intentional collisions. (CVE-2012-5371)

Input validation vulnerabilities were discovered in rubygem-activerecord. A remote attacker could possibly use these flaws to perform a SQL injection attack against an application using rubygem-activerecord. (CVE-2012-2661, CVE-2012-2695, CVE-2013-0155)

Input validation vulnerabilities were discovered in rubygem-actionpack. A remote attacker could possibly use these flaws to perform a SQL injection attack against an application using rubygem-actionpack and rubygem-activerecord. (CVE-2012-2660, CVE-2012-2694)

A flaw was found in the HTTP digest authentication implementation in rubygem-actionpack. A remote attacker could use this flaw to cause a denial of service of an application using rubygem-actionpack and digest authentication. (CVE-2012-3424)

A flaw was found in the handling of strings in Ruby safe level 4. A remote attacker can use Exception#to_s to destructively modify an untainted string so that it is tainted, the string can then be arbitrarily modified. (CVE-2012-4466)

A flaw was found in the method for translating an exception message into a string in the Ruby Exception class. A remote attacker could use this flaw to bypass safe level 4 restrictions, allowing untrusted (tainted) code to modify arbitrary, trusted (untainted) strings, which safe level 4 restrictions would otherwise prevent. (CVE-2012-4464)

It was found that ruby_parser from rubygem-ruby_parser created a temporary file in an insecure way. A local attacker could use this flaw to perform a symbolic link attack, overwriting arbitrary files accessible to the application using ruby_parser. (CVE-2013-0162)

The CVE-2013-0162 issue was discovered by Michael Scherer of the Red Hat Regional IT team.

Users are advised to upgrade to Red Hat OpenShift Enterprise 1.1.1.

ruby19 was updated to fix various bugs and security issues: Update to 1.9.3 p385 (bnc#802406)

  - XSS exploit of RDoc documentation generated by rdoc     (CVE-2013-0256)

  - for other changes see     /usr/share/doc/packages/ruby19/Changelog

Update to 1.9.3 p327 (bnc#789983)

  - CVE-2012-5371 and plenty of other fixes

Update to 1.9.3 p286 (bnc#783511, bnc#791199)

  - This release includes some security fixes, and many     other bug fixes. $SAFE escaping vulnerability about     Exception#to_s / NameError#to_s (CVE-2012-4464,     CVE-2012-4466)

  - Unintentional file creation caused by inserting an     illegal NUL character many other bug fixes.
    (CVE-2012-4522) Also following bugfixes and packaging     fixes were done :

  - make sure the rdoc output is more stable for     build-compare (new patch ruby-sort-rdoc-output.patch)

  - readd the private header *atomic.h

  - remove build depencency on ca certificates - only     causing cycles

  - one more header needed for rubygem-ruby-debug-base19

  - install vm_core.h and its dependencies as     ruby-devel-extra

  - move the provides to the ruby package instead

  - add provides for the internal gems

  - restore the old ruby macros and the gem wrapper script

  - gem_install_wrapper no longer necessary

This update of ruby fixed multiple SAFE level bypass flaws.

The ruby interpreter received a fix for two security issues :

  - Ruby's $SAFE mechanism enables untrusted user codes to     run in $SAFE >= 4 mode. This is a kind of sandboxing so     some operations are restricted in that mode to protect     other data outside the sandbox. (CVE-2012-4466)

    The problem found was around this mechanism.
    Exception#to_s, NameError#to_s, and name_err_mesg_to_s()     interpreter-internal API was not correctly handling the     $SAFE bits so a String object which is not tainted can     destructively be marked as tainted using them. By using     this an untrusted code in a sandbox can modify a     formerly-untainted string destructively.

    http://www.ruby-lang.org/en/news/2012/10/12/cve-2012-446     4-cve-2012-4466/

  - Ruby before 1.8.7-p352 does not reset the random seed     upon forking, which makes it easier for     context-dependent attackers to predict the values of     random numbers by leveraging knowledge of the number     sequence obtained in a different child process.
    (CVE-2011-2686)

  - Fix entity expansion DoS vulnerability in REXML. When     reading text nodes from an XML document, the REXML     parser could be coerced into allocating extremely large     string objects which could consume all available memory     on the system. (CVE-2013-1821)

The ruby interpreter received a fix for a security issue :

  - Ruby's $SAFE mechanism enables untrusted user codes to     run in $SAFE >= 4 mode. This is a kind of sandboxing so     some operations are restricted in that mode to protect     other data outside the sandbox. (CVE-2012-4466)

    The problem found was around this mechanism.
    Exception#to_s, NameError#to_s, and name_err_mesg_to_s()     interpreter-internal API was not correctly handling the     $SAFE bits so a String object which is not tainted can     destructively be marked as tainted using them. By using     this an untrusted code in a sandbox can modify a     formerly-untainted string destructively.

    http://www.ruby-lang.org/en/news/2012/10/12/cve-2012-446     4-cve-2012-4466/

The official ruby site reports :

Vulnerabilities found for Exception#to_s, NameError#to_s, and name_err_mesg_to_s() which is Ruby interpreter-internal API. A malicious user code can bypass $SAFE check by utilizing one of those security holes.

Ruby's $SAFE mechanism enables untrusted user codes to run in $SAFE >= 4 mode. This is a kind of sandboxing so some operations are restricted in that mode to protect other data outside the sandbox.

The problem found was around this mechanism. Exception#to_s, NameError#to_s, and name_err_mesg_to_s() interpreter-internal API was not correctly handling the $SAFE bits so a String object which is not tainted can destructively be marked as tainted using them. By using this an untrusted code in a sandbox can modify a formerly-untainted string destructively.

Ruby 1.8 once had a similar security issue. It fixed Exception#to_s and NameError#to_s, but name_err_mesg_to_str() issue survived previous security fix

Tyler Hicks and Shugo Maeda discovered that Ruby incorrectly allowed untainted strings to be modified in protective safe levels. An attacker could use this flaw to bypass intended access restrictions.
USN-1602-1 fixed these vulnerabilities in other Ubuntu releases. This update provides the corresponding updates for Ubuntu 12.10.
(CVE-2012-4464, CVE-2012-4466)

Peter Bex discovered that Ruby incorrectly handled file path strings when opening files. An attacker could use this flaw to open or create unexpected files. (CVE-2012-4522).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Some security flaws were found on ruby currently shipped on Fedora 17 where malicious user can bypass safe mechanize by raising exception intentionally and make arbitrary strings tainted. This flaw were now registered as CVE-2012-4464 and CVE-2012-4466.

Note that CVE-2012-4464 is basically the same as CVE-2011-1005, which was supposed to be already fixed on ruby 1.8.x branch but it proved that the fix was incomplete.

This new rpm will fix the above issue.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Some security flaws were found on ruby currently shipped on Fedora 17 where malicious user can bypass safe mechanize by raising exception intentionally and make arbitrary strings tainted. This flaw were now registered as CVE-2012-4464 and CVE-2012-4466.

This update rpm will fix this issue.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Tyler Hicks and Shugo Maeda discovered that Ruby incorrectly allowed untainted strings to be modified in protective safe levels. An attacker could use this flaw to bypass intended access restrictions.
(CVE-2012-4464, CVE-2012-4466).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Some security flaws were found on ruby currently shipped on Fedora 18 where malicious user can bypass safe mechanize by raising exception intentionally and make arbitrary strings tainted. This flaw were now registered as CVE-2012-4464 and CVE-2012-4466.

This update rpm will fix this issue.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
124931	EulerOS Virtualization 3.0.1.0 : ruby (EulerOS-SA-2019-1428)	Nessus	Huawei Local Security Checks	critical
119432	RHEL 6 : openshift (RHSA-2013:0582)	Nessus	Red Hat Local Security Checks	high
74909	openSUSE Security Update : ruby19 (openSUSE-SU-2013:0376-1)	Nessus	SuSE Local Security Checks	medium
74804	openSUSE Security Update : ruby / ruby19 (openSUSE-SU-2012:1443-1)	Nessus	SuSE Local Security Checks	medium
65799	SuSE 10 Security Update : ruby (ZYPP Patch Number 8524)	Nessus	SuSE Local Security Checks	medium
65248	SuSE 11.2 Security Update : ruby (SAT Patch Number 7386)	Nessus	SuSE Local Security Checks	medium
62791	FreeBSD : ruby -- $SAFE escaping vulnerability about Exception#to_s/NameError#to_s (2a093853-2495-11e2-b0c7-000d601460a4)	Nessus	FreeBSD Local Security Checks	medium
62661	Ubuntu 12.04 LTS / 12.10 : ruby1.9.1 vulnerabilities (USN-1614-1)	Nessus	Ubuntu Local Security Checks	medium
62531	Fedora 16 : ruby-1.8.7.358-4.fc16 (2012-15507)	Nessus	Fedora Local Security Checks	medium
62528	Fedora 17 : ruby-1.9.3.194-17.fc17 (2012-15395)	Nessus	Fedora Local Security Checks	medium
62496	Ubuntu 12.04 LTS : ruby1.9.1 vulnerabilities (USN-1602-1)	Nessus	Ubuntu Local Security Checks	medium
62455	Fedora 18 : ruby-1.9.3.194-18.fc18 (2012-15376)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2012-4464

high

Tenable Plugins

critical

high

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium