USN-3553-1: Ruby vulnerabilities
31 January 2018
Several security issues were fixed in Ruby.
- ruby2.3 - Interpreter of object-oriented scripting language Ruby
It was discovered that Ruby failed to validate specification names.
An attacker could possibly use a maliciously crafted gem to potentially
overwrite any file on the filesystem. (CVE-2017-0901)
It was discovered that Ruby was vulnerable to a DNS hijacking vulnerability.
An attacker could use this to possibly force the RubyGems client to download
and install gems from a server that the attacker controls. (CVE-2017-0902)
It was discovered that Ruby incorrectly handled certain YAML files. An attacker could
use this to possibly execute arbitrary code. (CVE-2017-0903)
The problem can be corrected by updating your system to the following package versions:
In general, a standard system update will make all the necessary changes.
- USN-3685-1: ruby2.0, ruby1.9.3, libtcltk-ruby1.9.1, ruby2.3, ruby2.0-doc, ruby2.3-doc, libruby2.3, ruby2.0-dev, ruby2.3-tcltk, ruby1.9.1-examples, ruby1.9.1-dev, ruby2.0-tcltk, libruby2.0, libruby1.9.1, ruby1.9.1-full, ruby2.3-dev, ri1.9.1, ruby1.9.1
- USN-3439-1: ruby1.9.3, libtcltk-ruby1.9.1, ruby1.9.1-examples, ruby1.9.1-dev, libruby1.9.1, ruby1.9.1-full, ri1.9.1, ruby1.9.1
- USN-3685-2: ruby2.0, ruby2.0-doc, ruby2.0-dev, ruby2.0-tcltk, libruby2.0