CVE-2009-3086: Infoleak
First published: Tue Sep 08 2009(Updated: )
A certain algorithm in Ruby on Rails 2.1.0 through 2.2.2, and 2.3.x before 2.3.4, leaks information about the complexity of message-digest signature verification in the cookie store, which might allow remote attackers to forge a digest via multiple attempts.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| rubygems/activesupport | >=2.3.0<2.3.4 | 2.3.4 |
| rubygems/actionpack | >=2.1.0<2.2.3 | 2.2.3 |
| rubygems/activesupport | >=2.1.0<2.2.3 | 2.2.3 |
| rubygems/actionpack | >=2.3.0<2.3.4 | 2.3.4 |
| Ruby on Rails | =2.1.0 | |
| Ruby on Rails | =2.1.1 | |
| Ruby on Rails | =2.1.2 | |
| Ruby on Rails | =2.2.0 | |
| Ruby on Rails | =2.2.1 | |
| Ruby on Rails | =2.2.2 | |
| Ruby on Rails | =2.3.2 | |
| Ruby on Rails | =2.3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2009-3086
- http://lists.opensuse.org/opensuse-security-announce/2009-10/msg00004.html
- http://weblog.rubyonrails.org/2009/9/4/timing-weakness-in-ruby-on-rails
- http://www.debian.org/security/2011/dsa-2260
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2009-3086.yml
- https://github.com/rails/rails/commit/1f07a89c5946910fc28ea5ccd1da6af8a0f972a0
- https://github.com/rails/rails/commit/674f780d59a5a7ec0301755d43a7b277a3ad2978
- https://github.com/rails/rails/commit/d460c9a25560f43e7c3789abadf7b455053eb686
- https://web.archive.org/web/20090906010200/http://www.vupen.com/english/advisories/2009/2544
- https://web.archive.org/web/20090907001716/http://secunia.com/advisories/36600
- https://web.archive.org/web/20200229150042/http://www.securityfocus.com/bid/37427
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activesupport/CVE-2009-3086.yml
- https://github.com/advisories/GHSA-fg9w-g6m4-557j (Advisory)
- http://secunia.com/advisories/36600
- http://www.securityfocus.com/bid/37427
- http://www.vupen.com/english/advisories/2009/2544
Frequently Asked Questions
What is the severity of CVE-2009-3086?
CVE-2009-3086 is classified as a medium severity vulnerability due to the potential for information disclosure and remote code execution via crafted requests.
How do I fix CVE-2009-3086?
To fix CVE-2009-3086, upgrade Ruby on Rails to version 2.3.4 or higher.
What versions of Ruby on Rails are affected by CVE-2009-3086?
CVE-2009-3086 affects Ruby on Rails versions 2.1.0 through 2.2.2 and all 2.3.x versions prior to 2.3.4.
Can CVE-2009-3086 be exploited remotely?
Yes, CVE-2009-3086 can be exploited remotely, allowing attackers to forge message-digest signatures.
What impact does CVE-2009-3086 have on security?
The impact of CVE-2009-3086 includes the potential for unauthorized access and manipulation of secured cookie data.
- collector/github-advisory-latest
- alias/GHSA-fg9w-g6m4-557j
- alias/CVE-2009-3086
- collector/github-advisory
- agent/author
- agent/type
- agent/softwarecombine
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/remedy
- agent/first-publish-date
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/nvd-historical
- package-manager/rubygems
- vendor/rubyonrails
- canonical/ruby on rails
- version/ruby on rails/2.1.0
- version/ruby on rails/2.1.1
- version/ruby on rails/2.1.2
- version/ruby on rails/2.2.0
- version/ruby on rails/2.2.1
- version/ruby on rails/2.2.2
- version/ruby on rails/2.3.2
- version/ruby on rails/2.3.3