Action Record in Ruby on Rails 4.2.x before 4.2.7.1 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, as demonstrated by certain [nil] values, a related issue to CVE-2012-2660, CVE-2012-2694, and CVE-2013-0155.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Rails | Rubyonrails | 4.2.0 (including) | 4.2.0 (including) |
Rails | Rubyonrails | 4.2.0-beta1 (including) | 4.2.0-beta1 (including) |
Rails | Rubyonrails | 4.2.0-beta2 (including) | 4.2.0-beta2 (including) |
Rails | Rubyonrails | 4.2.0-beta3 (including) | 4.2.0-beta3 (including) |
Rails | Rubyonrails | 4.2.0-beta4 (including) | 4.2.0-beta4 (including) |
Rails | Rubyonrails | 4.2.0-rc1 (including) | 4.2.0-rc1 (including) |
Rails | Rubyonrails | 4.2.0-rc2 (including) | 4.2.0-rc2 (including) |
Rails | Rubyonrails | 4.2.0-rc3 (including) | 4.2.0-rc3 (including) |
Rails | Rubyonrails | 4.2.1 (including) | 4.2.1 (including) |
Rails | Rubyonrails | 4.2.1-rc1 (including) | 4.2.1-rc1 (including) |
Rails | Rubyonrails | 4.2.1-rc2 (including) | 4.2.1-rc2 (including) |
Rails | Rubyonrails | 4.2.1-rc3 (including) | 4.2.1-rc3 (including) |
Rails | Rubyonrails | 4.2.1-rc4 (including) | 4.2.1-rc4 (including) |
Rails | Rubyonrails | 4.2.2 (including) | 4.2.2 (including) |
Rails | Rubyonrails | 4.2.3 (including) | 4.2.3 (including) |
Rails | Rubyonrails | 4.2.3-rc1 (including) | 4.2.3-rc1 (including) |
Rails | Rubyonrails | 4.2.4 (including) | 4.2.4 (including) |
Rails | Rubyonrails | 4.2.4-rc1 (including) | 4.2.4-rc1 (including) |
Rails | Rubyonrails | 4.2.5 (including) | 4.2.5 (including) |
Rails | Rubyonrails | 4.2.5-rc1 (including) | 4.2.5-rc1 (including) |
Rails | Rubyonrails | 4.2.5-rc2 (including) | 4.2.5-rc2 (including) |
Rails | Rubyonrails | 4.2.5.1 (including) | 4.2.5.1 (including) |
Rails | Rubyonrails | 4.2.5.2 (including) | 4.2.5.2 (including) |
Rails | Rubyonrails | 4.2.6 (including) | 4.2.6 (including) |
Rails | Rubyonrails | 4.2.6-rc1 (including) | 4.2.6-rc1 (including) |
Rails | Rubyonrails | 4.2.7 (including) | 4.2.7 (including) |
Rails | Rubyonrails | 4.2.7-rc1 (including) | 4.2.7-rc1 (including) |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-ror42-rubygem-actionpack-1:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-ror42-rubygem-actionview-0:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-ror42-rubygem-activerecord-1:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.1 EUS | RedHat | rh-ror42-rubygem-actionpack-1:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.1 EUS | RedHat | rh-ror42-rubygem-actionview-0:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.1 EUS | RedHat | rh-ror42-rubygem-activerecord-1:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.2 EUS | RedHat | rh-ror42-rubygem-actionpack-1:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.2 EUS | RedHat | rh-ror42-rubygem-actionview-0:4.2.6-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.2 EUS | RedHat | rh-ror42-rubygem-activerecord-1:4.2.6-3.el7 | * |
Rails | Ubuntu | artful | * |
Rails | Ubuntu | yakkety | * |
Rails | Ubuntu | zesty | * |
Ruby-actionpack-2.3 | Ubuntu | precise | * |
Ruby-actionpack-2.3 | Ubuntu | upstream | * |
Ruby-activerecord-2.3 | Ubuntu | precise | * |
Ruby-activerecord-2.3 | Ubuntu | upstream | * |
Ruby-activesupport-2.3 | Ubuntu | precise | * |
Ruby-activesupport-2.3 | Ubuntu | upstream | * |
Ruby-rails-2.3 | Ubuntu | precise | * |
Ruby-rails-2.3 | Ubuntu | upstream | * |
Ruby-rails-3.2 | Ubuntu | trusty | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: