rubygems -- deserialization vulnerabilityentered 2017-10-10
no CVE referenced
RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a possible remote code execution vulnerability. YAML deserialization of gem specifications can bypass class white lists. Specially crafted serialized objects can possibly be used to escalate to remote code execution.
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| devel/rubygem-gems | rubygem-gems | 2.0.0 | unaddressed | ruby@FreeBSD.org |
no CVE referenced
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>rubygem-gems</name>
<range><lt>FIXME</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>RubyGems versions between 2.0.0 and 2.6.13 are vulnerable to a
possible remote code execution vulnerability. YAML deserialization of
gem specifications can bypass class white lists. Specially crafted
serialized objects can possibly be used to escalate to remote code
execution.</p>
</body>
</description>
<references>
<cvename>CVE-2017-0903</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2017-0903</url>
</references>
<dates>
<discovery>2017-10-11</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>