CVE-2011-0447: Ruby on Rails 2.1.x, 2.2.x, and 2.3.x before 2.3.11, and 3.x before 3.0.4, does not properly validate HTTP requests that contain an…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.2% of all records.
- Fixed version: rails (Debian:12) 2.3.11-0.1; rails (Debian:5.0) 2.1.0-7+lenny0.1; rails (Debian:6.0) 2.3.5-1.2+squeeze0.1.
Low priority for now. Upgrade to rails (Debian:12) 2.3.11-0.1; rails (Debian:5.0) 2.1.0-7+lenny0.1; rails (Debian:6.0) 2.3.5-1.2+squeeze0.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Ruby on Rails 2.1.x, 2.2.x, and 2.3.x before 2.3.11, and 3.x before 3.0.4, does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged (1) AJAX or (2) API requests that leverage "combinations of browser plugins and HTTP redirects," a related issue to CVE-2011-0696.
- Published
- Feb 14, 2011
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 73th percentile
- CWE
- CWE-352
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rubyonrails | rails | cpe:2.3:a:rubyonrails:rails |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- 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.10
- rubyonrails rails2.3.2
+8 more rows
- rubyonrails rails2.3.3
- rubyonrails rails2.3.4
- rubyonrails rails2.3.9
- rubyonrails rails3.0.0
- rubyonrails rails3.0.1
- rubyonrails rails3.0.2
- rubyonrails rails3.0.3
- rubyonrails rails3.0.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rails | before 2.3.11-0.1 | 2.3.11-0.1 |
| Debian:5.0 | rails | before 2.1.0-7+lenny0.1 | 2.1.0-7+lenny0.1 |
| Debian:6.0 | rails | before 2.3.5-1.2+squeeze0.1 | 2.3.5-1.2+squeeze0.1 |
| RubyGems | actionpack | from 2.1.0 · before 2.3.11 | 2.3.11 |
| RubyGems | actionpack | from 3.0.0 · before 3.0.4 | 3.0.4 |
Same product
rubyonrails: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-5418There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted…KEV90Now
- CVE-2016-0752Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1…KEV89Now
- CVE-2019-5420A remote code execution vulnerability in development mode Rails <5.2.2.1, <6.0.0.beta3 can allow an attacker to guess the automatically…66This week
Published before and after this one in the same product
- ← EarlierCVE-2010-3933Oct 27, 2010 · Ruby on Rails 2.3.9 and 3.0.0 does not properly handle nested attributes, which allows remote attackers to modify arbitrary records by…26Monitor
- ← EarlierCVE-2011-0446Feb 14, 2011 · Multiple cross-site scripting (XSS) vulnerabilities in the mail_to helper in Ruby on Rails before 2.3.11, and 3.x before 3.0.4, when…18Monitor
- Later →CVE-2011-0448Feb 21, 2011 · Ruby on Rails 3.0.x before 3.0.4 does not ensure that arguments to the limit function specify integer values, which makes it easier for…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:rails | 2.3.11-0.1 · Debian:12 | Package registry (OSV) |
| RubyGems:actionpack | 2.3.11 | Package registry (OSV) |
| RubyGems:actionpack | 3.0.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- groups.google.com/group/rubyonrails-security/msg/c22ea1668c0d181c?dmode=source&output=gplain
- lists.fedoraproject.org/pipermail/package-announce/2011-April/057650.html
- lists.fedoraproject.org/pipermail/package-announce/2011-March/055088.html
- secunia.com/advisories/43274
- secunia.com/advisories/43666
- weblog.rubyonrails.org/2011/2/8/csrf-protection-bypass-in-ruby-on-rails
- www.debian.org/security/2011/dsa-2247
- www.securityfocus.com/bid/46291
- www.securitytracker.com/id?1025060
- www.vupen.com/english/advisories/2011/0587
- www.vupen.com/english/advisories/2011/0877
Vendor advisories and official records. Exploit/PoC links are deliberately left out.