First published: Thu Apr 24 2014(Updated: )
** DISPUTED ** The openssl extension in Ruby 2.x does not properly maintain the state of process memory after a file is reopened, which allows remote attackers to spoof signatures within the context of a Ruby script that attempts signature verification after performing a certain sequence of filesystem operations. NOTE: this issue has been disputed by the Ruby OpenSSL team and third parties, who state that the original demonstration PoC contains errors and redundant or unnecessarily-complex code that does not appear to be related to a demonstration of the issue. As of 20140502, CVE is not aware of any public comment by the original researcher.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Ruby | =2.0 | |
Ruby | =2.0.0 | |
Ruby | =2.0.0-p0 | |
Ruby | =2.0.0-p195 | |
Ruby | =2.0.0-p247 | |
Ruby | =2.0.0-preview1 | |
Ruby | =2.0.0-preview2 | |
Ruby | =2.0.0-rc1 | |
Ruby | =2.0.0-rc2 | |
Ruby | =2.1 | |
Ruby | =2.1-preview1 | |
Ruby | =2.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-2734 is considered a medium severity vulnerability due to potential spoofing risks.
To remediate CVE-2014-2734, upgrade Ruby to a version that includes the fix for this vulnerability.
CVE-2014-2734 affects Ruby versions 2.0.x and 2.1.x.
Yes, CVE-2014-2734 allows remote attackers to spoof signatures, creating a potential remote exploitation vector.
CVE-2014-2734 is not persistent as it requires specific conditions related to file handling in Ruby.