Skip to content
Fencer Intel
high 7.5

CVE-2016-6317 json

ActiveRecord in Ruby on Rails allows database-query bypass

published 2016-09-07 10 y ago modified 2026-06-17 4 mo ago also GHSA-pr3r-4wrp-r2pv , EUVD-2017-0283

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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.

Patch / fix

  • rubygems activerecord 4.2.7.1
  • rails Debian 14, Debian 13, Debian 12 2:4.2.7.1-1

debian advisories DEBIAN-CVE-2016-6317

  • rh-ror42-rubygem-actionpack RHEL 2 SOFTWARE_COLLECTIONS 1:4.2.6-3.el7
  • rh-ror42-rubygem-actionview RHEL 2 SOFTWARE_COLLECTIONS 4.2.6-3.el7
  • rh-ror42-rubygem-activerecord RHEL 2 SOFTWARE_COLLECTIONS 1:4.2.6-3.el7

red hat advisories RHSA-2016:1855

  • rubygem-rails-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-3.3.1
  • rubygem-railties-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-3.3.1
  • rubygem-activejob-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-3.3.1
  • rubygem-actionpack-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-7.3.1
  • rubygem-actionview-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-9.3.1
  • rubygem-activemodel-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-6.3.1
  • rubygem-actionmailer-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-3.3.1
  • rubygem-activerecord-4_2 OpenStack Cloud 7, OpenStack Cloud 6, Enterprise Storage 4 +1 more 4.2.9-6.3.1

suse advisories SUSE-SU-2017:2716-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-6317 updated cvss 5.3

rubygem-activerecord: unsafe query generation in Active Record

  • Red Hat Software Collections for Red Hat Enterprise Linux Server (v. 7) rh-ror42-rubygem-actionpack 4.2.6-3.el7, rh-ror42-rubygem-actionview 4.2.6-3.el7, rh-ror42-rubygem-activerecord 4.2.6-3.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.1) rh-ror42-rubygem-actionpack 4.2.6-3.el7, rh-ror42-rubygem-actionview 4.2.6-3.el7, rh-ror42-rubygem-activerecord 4.2.6-3.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.2) rh-ror42-rubygem-actionpack 4.2.6-3.el7, rh-ror42-rubygem-actionview 4.2.6-3.el7, rh-ror42-rubygem-activerecord 4.2.6-3.el7 Red Hat Software Collections for Red Hat Enterprise Linux Workstation (v. 7) rh-ror42-rubygem-actionpack 4.2.6-3.el7, rh-ror42-rubygem-actionview 4.2.6-3.el7, rh-ror42-rubygem-activerecord 4.2.6-3.el7
    fixed: vendor fix RHSA-2016:1855
  • Red Hat OpenStack Foreman ruby193-rubygem-activerecord Red Hat Software Collections ror40-rubygem-activerecord, ruby193-rubygem-activerecord, rh-ror41-rubygem-activerecord Red Hat Subscription Asset Manager rubygem-activerecord, ruby193-rubygem-activerecord
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.90% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems activerecord
>=4.2.0, <4.2.7.1
4.2.7.1

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.