medium
6.4
CWE
20
Advisory Published
Updated

CVE-2013-3221: Input Validation

First published: Mon Apr 22 2013(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Ruby on Rails=2.3.0
Ruby on Rails=2.3.1
Ruby on Rails=2.3.2
Ruby on Rails=2.3.3
Ruby on Rails=2.3.4
Ruby on Rails=2.3.9
Ruby on Rails=2.3.10
Ruby on Rails=2.3.11
Ruby on Rails=2.3.12
Ruby on Rails=2.3.13
Ruby on Rails=2.3.14
Ruby on Rails=2.3.15
Ruby on Rails=2.3.16
Ruby on Rails=3.0.0
Ruby on Rails=3.0.0-beta
Ruby on Rails=3.0.0-beta2
Ruby on Rails=3.0.0-beta3
Ruby on Rails=3.0.0-beta4
Ruby on Rails=3.0.0-rc
Ruby on Rails=3.0.0-rc2
Ruby on Rails=3.0.1
Ruby on Rails=3.0.1-pre
Ruby on Rails=3.0.2
Ruby on Rails=3.0.2-pre
Ruby on Rails=3.0.3
Ruby on Rails=3.0.4-rc1
Ruby on Rails=3.0.5
Ruby on Rails=3.0.5-rc1
Ruby on Rails=3.0.6
Ruby on Rails=3.0.6-rc1
Ruby on Rails=3.0.6-rc2
Ruby on Rails=3.0.7
Ruby on Rails=3.0.7-rc1
Ruby on Rails=3.0.7-rc2
Ruby on Rails=3.0.8
Ruby on Rails=3.0.8-rc1
Ruby on Rails=3.0.8-rc2
Ruby on Rails=3.0.8-rc3
Ruby on Rails=3.0.8-rc4
Ruby on Rails=3.0.9
Ruby on Rails=3.0.9-rc1
Ruby on Rails=3.0.9-rc2
Ruby on Rails=3.0.9-rc3
Ruby on Rails=3.0.9-rc4
Ruby on Rails=3.0.9-rc5
Ruby on Rails=3.0.10
Ruby on Rails=3.0.10-rc1
Ruby on Rails=3.0.11
Ruby on Rails=3.0.12
Ruby on Rails=3.0.12-rc1
Ruby on Rails=3.0.13
Ruby on Rails=3.0.13-rc1
Ruby on Rails=3.0.14
Ruby on Rails=3.0.16
Ruby on Rails=3.0.17
Ruby on Rails=3.0.18
Ruby on Rails=3.0.19
Ruby on Rails=3.0.20
Ruby on Rails=3.0.4
Ruby on Rails=3.1.0
Ruby on Rails=3.1.0-beta1
Ruby on Rails=3.1.0-rc1
Ruby on Rails=3.1.0-rc2
Ruby on Rails=3.1.0-rc3
Ruby on Rails=3.1.0-rc4
Ruby on Rails=3.1.0-rc5
Ruby on Rails=3.1.0-rc6
Ruby on Rails=3.1.0-rc7
Ruby on Rails=3.1.0-rc8
Ruby on Rails=3.1.1
Ruby on Rails=3.1.1-rc1
Ruby on Rails=3.1.1-rc2
Ruby on Rails=3.1.1-rc3
Ruby on Rails=3.1.2
Ruby on Rails=3.1.2-rc1
Ruby on Rails=3.1.2-rc2
Ruby on Rails=3.1.3
Ruby on Rails=3.1.4
Ruby on Rails=3.1.4-rc1
Ruby on Rails=3.1.5
Ruby on Rails=3.1.5-rc1
Ruby on Rails=3.1.6
Ruby on Rails=3.1.7
Ruby on Rails=3.1.8
Ruby on Rails=3.1.9
Ruby on Rails=3.1.10
Ruby on Rails=3.2.0
Ruby on Rails=3.2.0-rc1
Ruby on Rails=3.2.0-rc2
Ruby on Rails=3.2.1
Ruby on Rails=3.2.2
Ruby on Rails=3.2.2-rc1
Ruby on Rails=3.2.3
Ruby on Rails=3.2.3-rc1
Ruby on Rails=3.2.3-rc2
Ruby on Rails=3.2.4
Ruby on Rails=3.2.4-rc1
Ruby on Rails=3.2.5
Ruby on Rails=3.2.6
Ruby on Rails=3.2.7
Ruby on Rails=3.2.8
Ruby on Rails=3.2.9
Ruby on Rails=3.2.10
Ruby on Rails=3.2.11

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-3221?

    CVE-2013-3221 is classified as a high-severity vulnerability due to the potential for data-type injection attacks that can compromise security.

  • How do I fix CVE-2013-3221?

    To mitigate CVE-2013-3221, upgrade to Ruby on Rails versions 3.2.12 or later, or apply the recommended patches provided in official advisories.

  • What impact does CVE-2013-3221 have on my application?

    CVE-2013-3221 can allow remote attackers to manipulate data types, possibly leading to unauthorized access or data corruption.

  • Who is affected by CVE-2013-3221?

    CVE-2013-3221 affects applications using Ruby on Rails versions 2.3.x, 3.0.x, 3.1.x, and 3.2.x.

  • Is CVE-2013-3221 exploitable in the wild?

    There have been reports suggesting that CVE-2013-3221 is actively being exploited in the wild, making immediate remediation essential.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203