ActiveRecord in Ruby on Rails allows database-query bypass
Published Sep 7, 2016 · Updated Oct 23, 2026 · Also known as GHSA-pr3r-4wrp-r2pv
Original summary
Normalized public record · Updated Oct 23, 2026
ActiveRecord in Ruby on Rails allows database-query bypass
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Active 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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- GHSA-pr3r-4wrp-r2pv
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- 92434 ↗
- [oss-security] 20160811 [CVE-2016-6317] Unsafe Query Generation Risk in Active Record ↗
- RHSA-2016:1855 ↗
- weblog.rubyonrails.org ↗
- [ruby-security-ann] 20160811 [CVE-2016-6317] Unsafe Query Generation Risk in Active Record ↗
Record history
Published Sep 7, 2016 · Last refreshed Oct 23, 2026