# CVE-2011-2930: activerecord vulnerable to SQL Injection

> Remote attackers can execute arbitrary SQL commands via crafted column names in Ruby on Rails ActiveRecord adapters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-2930, GHSA-h6w6-xmqv-7q78

## What is CVE-2011-2930?

CVE-2011-2930 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Aug 2011. It can be exploited over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2011-2930?

6 open source packages ship an affected version, including activerecord. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `activerecord` | RubyGems | From 2.0.0 | 2.3.13 |
| `activerecord` | RubyGems | From 2.0.0 | 2.3.13 |
| `activerecord` | RubyGems | From 3.0.0.beta | 3.0.10 |
| `activerecord` | RubyGems | From 3.0.0.beta | 3.0.10 |
| `activerecord` | RubyGems | From 3.1.0.beta1 | 3.1.0.rc5 |
| `activerecord` | RubyGems | From 3.1.0.beta1 | 3.1.0.rc5 |

Products: Rubyonrails Rails, Rubyonrails Ruby on Rails.

## How do I fix CVE-2011-2930?

Upgrade activerecord to a fixed version for your release line: 2.3.13, 3.0.10 or 3.1.0.rc5.

## Is CVE-2011-2930 being exploited?

There is no known exploitation of CVE-2011-2930 in the wild and no public exploit code.

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2930 and fix it if it is affected.

What it is: CVE-2011-2930 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Aug 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2930 in the wild and no public exploit code.

Affected packages and fixed versions:
- activerecord (RubyGems): affected from 2.0.0; fixed in 2.3.13
- activerecord (RubyGems): affected from 2.0.0; fixed in 2.3.13
- activerecord (RubyGems): affected from 3.0.0.beta; fixed in 3.0.10
- activerecord (RubyGems): affected from 3.0.0.beta; fixed in 3.0.10
- activerecord (RubyGems): affected from 3.1.0.beta1; fixed in 3.1.0.rc5
- activerecord (RubyGems): affected from 3.1.0.beta1; fixed in 3.1.0.rc5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-2930/ (Markdown: https://insights.sbomify.com/CVE-2011-2930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-2930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-2930
- OSV: https://osv.dev/vulnerability/CVE-2011-2930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-2930/
Summaries are generated and may contain mistakes; the official description above is the record.