Multiple denial of service flaws were found in the way the Ruby REXML XML parser performed expansion of parameter entities. A specially crafted XML document could cause REXML to use an excessive amount of CPU and memory. (CVE-2014-8080, CVE-2014-8090)

All running instances of Ruby need to be restarted for this update to take effect.

This ruby update fixes the following two security issues :

  - bnc#902851: fix CVE-2014-8080: Denial Of Service XML     Expansion

  - bnc#905326: fix CVE-2014-8090: Another Denial Of Service     XML Expansion

  - Enable tests to run during the build. This way we can     compare the results on different builds.

The following issues were fixed in this update :

  - CVE-2014-8090: Denial Of Service XML Expansion     (bnc#905326)

  - CVE-2014-8080: Denial Of Service XML Expansion     (bnc#902851)

It was discovered that the REXML parser, part of the interpreter for the Ruby language, could be coerced into allocating large string objects that could consume all available memory on the system. This could allow remote attackers to cause a denial of service (crash).

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.

Updated ruby packages fix security vulnerabilities :

Will Wood discovered that Ruby incorrectly handled the encodes() function. An attacker could possibly use this issue to cause Ruby to crash, resulting in a denial of service, or possibly execute arbitrary code. The default compiler options for affected releases should reduce the vulnerability to a denial of service (CVE-2014-4975).

Due to an incomplete fix for CVE-2014-8080, 100% CPU utilization can occur as a result of recursive expansion with an empty String. When reading text nodes from an XML document, the REXML parser in Ruby can be coerced into allocating extremely large string objects which can consume all of the memory on a machine, causing a denial of service (CVE-2014-8090).

Additionally ruby has been upgraded to patch level 374.

ruby19 was updated to fix two security issues.

These security issues were fixed :

  - Denial Of Service XML Expansion (CVE-2014-8080).

  - Denial Of Service XML Expansion (CVE-2014-8090).

Note: These are two separate issues.

ID	名稱	產品	系列	已發布	已更新	嚴重性
79657	Scientific Linux Security Update : ruby on SL6.x i386/x86_64 (20141126)	Nessus	Scientific Linux Local Security Checks	2014/12/2	2021/1/14	medium
80353	openSUSE Security Update : ruby20 (openSUSE-SU-2015:0002-1)	Nessus	SuSE Local Security Checks	2015/1/5	2021/1/19	medium
80356	openSUSE Security Update : ruby2.1 (openSUSE-SU-2015:0007-1)	Nessus	SuSE Local Security Checks	2015/1/5	2021/1/19	medium
81279	Debian DSA-3159-1 : ruby1.8 - security update	Nessus	Debian Local Security Checks	2015/2/11	2021/1/11	medium
124931	EulerOS Virtualization 3.0.1.0 : ruby (EulerOS-SA-2019-1428)	Nessus	Huawei Local Security Checks	2019/5/14	2024/5/23	critical
79571	Mandriva Linux Security Advisory : ruby (MDVSA-2014:225)	Nessus	Mandriva Local Security Checks	2014/11/26	2021/1/6	medium
79820	openSUSE Security Update : ruby19 (openSUSE-SU-2014:1589-1)	Nessus	SuSE Local Security Checks	2014/12/9	2021/1/19	medium

偵測

搜尋 Plugin

medium

medium

medium

medium

critical

medium

medium