CVE-2013-3221

UnknownEPSS 1.96%

Last modified

CVE-2013-3221 is a vulnerability of currently unknown severity. The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database.. EPSS estimates a 1.96% chance of exploitation in the next 30 days.

Description

The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database.

Metrics

EPSS Probability
1.96%

77.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
RubyonrailsRails2.3.0
RubyonrailsRails2.3.1
RubyonrailsRails2.3.2
RubyonrailsRails2.3.3
RubyonrailsRails2.3.4
RubyonrailsRails2.3.9
RubyonrailsRails2.3.10
RubyonrailsRails2.3.11
RubyonrailsRails2.3.12
RubyonrailsRails2.3.13
RubyonrailsRails2.3.14
RubyonrailsRails2.3.15
RubyonrailsRails2.3.16
RubyonrailsRails3.0.0
RubyonrailsRails3.0.1
RubyonrailsRails3.0.2
RubyonrailsRails3.0.3
RubyonrailsRails3.0.4Rc1
RubyonrailsRails3.0.5
RubyonrailsRails3.0.6
RubyonrailsRails3.0.7
RubyonrailsRails3.0.8
RubyonrailsRails3.0.9
RubyonrailsRails3.0.10
RubyonrailsRails3.0.11
RubyonrailsRails3.0.12
RubyonrailsRails3.0.13
RubyonrailsRails3.0.14
RubyonrailsRails3.0.16
RubyonrailsRails3.0.17
RubyonrailsRails3.0.18
RubyonrailsRails3.0.19
RubyonrailsRails3.0.20
RubyonrailsRuby On Rails3.0.4
RubyonrailsRails3.1.0
RubyonrailsRails3.1.1
RubyonrailsRails3.1.2
RubyonrailsRails3.1.3
RubyonrailsRails3.1.4
RubyonrailsRails3.1.5
RubyonrailsRails3.1.6
RubyonrailsRails3.1.7
RubyonrailsRails3.1.8
RubyonrailsRails3.1.9
RubyonrailsRails3.1.10
RubyonrailsRails3.2.0
RubyonrailsRails3.2.1
RubyonrailsRails3.2.2
RubyonrailsRails3.2.3
RubyonrailsRails3.2.4

Showing 50 of 57 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-3221?
The Active Record component in Ruby on Rails 2.3.x, 3.0.x, 3.1.x, and 3.2.x does not ensure that the declared data type of a database column is used during comparisons of input values to stored values in that column, which makes it easier for remote attackers to conduct data-type injection attacks against Ruby on Rails applications via a crafted value, as demonstrated by unintended interaction between the "typed XML" feature and a MySQL database.
How severe is CVE-2013-3221?
Severity scoring for CVE-2013-3221 is pending analysis. The EPSS model estimates a 1.96% probability of exploitation in the next 30 days.
How do I fix CVE-2013-3221?
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.

Are you affected by CVE-2013-3221?

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

Scan your code now

Source: NVD / NIST