Summary
Array data injection vulnerability in activerecord
SQL injection vulnerability in activerecord/lib/active_record/connection_adapters/postgresql/cast.rb in Active Record in Ruby on Rails 4.0.x before 4.0.3, and 4.1.0.beta1, when PostgreSQL is used, allows remote attackers to execute "add data" SQL commands via vectors involving \ (backslash) characters that are not properly handled in operations on array columns.
Impact
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
activerecord to 4.0.3 or later; activerecord to 4.1.0.beta2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2014-0080? CVE-2014-0080 is a medium-severity SQL injection vulnerability in activerecord (rubygems), affecting versions >= 4.0.0, < 4.0.3. It is fixed in 4.0.3, 4.1.0.beta2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of activerecord are affected by CVE-2014-0080? activerecord (rubygems) versions >= 4.0.0, < 4.0.3 is affected.
- Is there a fix for CVE-2014-0080? Yes. CVE-2014-0080 is fixed in 4.0.3, 4.1.0.beta2. Upgrade to this version or later.
- Is CVE-2014-0080 exploitable, and should I be worried? Whether CVE-2014-0080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2014-0080 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2014-0080?
- Upgrade
activerecordto 4.0.3 or later - Upgrade
activerecordto 4.1.0.beta2 or later
- Upgrade