CVE-2013-6417: Medium severity rubyonrails Rails vulnerability
actionpack/lib/actiondispatch/http/request.rb in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155.
Other sources
actionpack/lib/actiondispatch/http/request.rb in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 does not properly consider differences in parameter handling between the Active Record component and the JSON implementation, which allows remote attackers to bypass intended database-query restrictions and perform NULL checks or trigger missing WHERE clauses via a crafted request that leverages (1) third-party Rack middleware or (2) custom Rack middleware. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-0155.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rubygems/actionpackto a version that resolves this vulnerability.Fixed in 4.0.2 - Upgrade
Upgrade
rubygems/actionpackto a version that resolves this vulnerability.Fixed in 3.2.16 - Upgrade
Upgrade
Ruby on Railsto a version that resolves this vulnerability.Fixed in 3.2.16 - Upgrade
Upgrade
Ruby on Railsto a version that resolves this vulnerability.Fixed in 4.0.2
Event History
Frequently Asked Questions
What is the severity of CVE-2013-6417?
CVE-2013-6417 has a severity rating that allows remote attackers to bypass database-query restrictions.
How do I fix CVE-2013-6417?
To fix CVE-2013-6417, you should upgrade to Ruby on Rails version 4.0.2 or 3.2.16 or later.
What components are affected by CVE-2013-6417?
CVE-2013-6417 affects the actionpack component in Ruby on Rails versions prior to 4.0.2 and 3.2.16.
Can CVE-2013-6417 affect database integrity?
Yes, CVE-2013-6417 can potentially allow unauthorized database queries, impacting database integrity.
Is CVE-2013-6417 a critical vulnerability?
CVE-2013-6417 is considered a significant vulnerability due to the ability to bypass intended security measures.