cve.bz

CVE-2011-2930 rubyonrails: SQL Injection

no score yetEPSS 2.3%Fix available

rubyonrails: no CVSS score yet. EPSS 2.3% estimated probability of exploitation activity in the next 30 days. Fixed in activerecord 2.3.13, 3.0.10, 3.1.0.rc5.

On this page
Multiple SQL injection vulnerabilities in the quote_table_name method in the ActiveRecord adapters in activerecord/lib/active_record/connection_adapters/ in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allow remote attackers to execute arbitrary SQL commands via a crafted column name.
EPSS
2.3% (unchanged from 2.3% a week ago; 2.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 84th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2011-2930 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2011-2930?via=ask-ai-copy and https://cve.bz/cve/CVE-2011-2930?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2011-2930 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
rubyonrails:rails2.0.0
rubyonrails:rails2.0.0:rc1
rubyonrails:rails2.0.0:rc2
rubyonrails:rails2.0.1
rubyonrails:rails2.0.2
rubyonrails:rails2.0.4
rubyonrails:rails2.1.0
rubyonrails:rails2.1.1
rubyonrails:rails2.1.2
rubyonrails:rails2.2.0
rubyonrails:rails2.2.1
rubyonrails:rails2.2.2
rubyonrails:rails2.3.2
rubyonrails:rails2.3.3
rubyonrails:rails2.3.4
rubyonrails:rails2.3.9
rubyonrails:rails2.3.10
rubyonrails:rails2.3.11
rubyonrails:rails2.3.12
rubyonrails:rails3.0.0
rubyonrails:rails3.0.0:beta
rubyonrails:rails3.0.0:beta2
rubyonrails:rails3.0.0:beta3
rubyonrails:rails3.0.0:beta4
rubyonrails:rails3.0.0:rc
rubyonrails:rails3.0.0:rc2
rubyonrails:rails3.0.1
rubyonrails:rails3.0.1:pre
rubyonrails:rails3.0.2
rubyonrails:rails3.0.2:pre
rubyonrails:rails3.0.3
rubyonrails:rails3.0.4:rc1
rubyonrails:rails3.0.5
rubyonrails:rails3.0.5:rc1
rubyonrails:rails3.0.6
rubyonrails:rails3.0.6:rc1
rubyonrails:rails3.0.6:rc2
rubyonrails:rails3.0.7
rubyonrails:rails3.0.7:rc1
rubyonrails:rails3.0.7:rc2
rubyonrails:rails3.0.8
rubyonrails:rails3.0.8:rc1
rubyonrails:rails3.0.8:rc2
rubyonrails:rails3.0.8:rc3
rubyonrails:rails3.0.8:rc4
rubyonrails:rails3.0.9
rubyonrails:rails3.0.9:rc1
rubyonrails:rails3.0.9:rc2
rubyonrails:rails3.0.9:rc3
rubyonrails:rails3.0.9:rc4
rubyonrails:rails3.0.9:rc5
rubyonrails:rails3.0.10:rc1
rubyonrails:rails3.1.0
rubyonrails:rails3.1.0:beta1
rubyonrails:rails3.1.0:rc1
rubyonrails:rails3.1.0:rc2
rubyonrails:rails3.1.0:rc3
rubyonrails:rails3.1.0:rc4
rubyonrails:ruby_on_rails3.0.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h6w6-xmqv-7q78RubyGemsactiverecord>=2.0.0 <2.3.132.3.13
GHSA-h6w6-xmqv-7q78RubyGemsactiverecord>=3.0.0.beta <3.0.103.0.10
GHSA-h6w6-xmqv-7q78RubyGemsactiverecord>=3.1.0.beta1 <3.1.0.rc53.1.0.rc5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian5.0rails2.1.0-7+lenny1DSA-2301-1
Debian6.0rails2.3.5-1.2+squeeze1DSA-2301-1
Debian12, 13, 14rails2.3.14DEBIAN-CVE-2011-2930

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON