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)
{ "availability": "No subscription required", "binaries": [ { "binary_version": "2.3.1-2~16.04.6", "binary_name": "libruby2.3" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "libruby2.3-dbg" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "libruby2.3-dbgsym" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-dbgsym" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-dev" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-dev-dbgsym" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-doc" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-tcltk" }, { "binary_version": "2.3.1-2~16.04.6", "binary_name": "ruby2.3-tcltk-dbgsym" } ] }