Strix
26.1K

CVE-2016-6317

UnknownEPSS 3.90%

Last modified

CVE-2016-6317 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.90% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
3.90%

88.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
RubyonrailsRails4.2.0
RubyonrailsRails4.2.1
RubyonrailsRails4.2.2
RubyonrailsRails4.2.3
RubyonrailsRails4.2.4
RubyonrailsRails4.2.5
RubyonrailsRails4.2.5.1
RubyonrailsRails4.2.5.2
RubyonrailsRails4.2.6
RubyonrailsRails4.2.7

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-6317?
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.
How severe is CVE-2016-6317?
Severity scoring for CVE-2016-6317 is pending analysis. The EPSS model estimates a 3.90% probability of exploitation in the next 30 days.
How do I fix CVE-2016-6317?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2016

View all 2016CVEs →

Are you affected by CVE-2016-6317?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST