CVE-2006-4111 rubyonrails: Code Injection
rubyonrails: no CVSS score yet. EPSS 2.3% estimated probability of exploitation activity in the next 30 days. Fixed in rails 1.1.6.
On this page
Ruby on Rails before 1.1.5 allows remote attackers to execute Ruby code with "severe" or "serious" impact via a File Upload request with an HTTP header that modifies the LOAD_PATH variable, a different vulnerability than CVE-2006-4112.
- 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-94 Improper Control of Generation of Code (Code Injection)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
rails(RubyGems): fixed in 1.1.6- Debian: fixed package versions per release
- Patch: http://blog.koehntopp.de/archives/1367-Ruby-On-Rails-Mandatory-Mystery-Patch.html
- Patch: http://weblog.rubyonrails.org/2006/8/9/rails-1-1-5-mandatory-security-patch-and-other-tidbits
- Patch: http://www.gentoo.org/security/en/glsa/glsa-200608-20.xml
- Vendor advisory: http://secunia.com/advisories/21466
- Vendor advisory: http://secunia.com/advisories/21749
- Vendor advisory: http://www.gentoo.org/security/en/glsa/glsa-200608-20.xml
Ask an AI about this CVE
Show the prompt
Explain CVE-2006-4111 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-4111?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-4111?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-2006-4111 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.
| Product | Affected |
|---|---|
| rubyonrails:rails | 0.9.1 |
| rubyonrails:rails | 0.9.2 |
| rubyonrails:rails | 0.9.3 |
| rubyonrails:rails | 0.9.4 |
| rubyonrails:rails | 0.9.4.1 |
| rubyonrails:rails | 0.10.0 |
| rubyonrails:rails | 0.10.1 |
| rubyonrails:rails | 0.11.0 |
| rubyonrails:rails | 0.11.1 |
| rubyonrails:rails | 0.12.0 |
| rubyonrails:rails | 0.12.1 |
| rubyonrails:rails | 0.13.0 |
| rubyonrails:rails | 0.13.1 |
| rubyonrails:rails | 0.14.1 |
| rubyonrails:rails | 0.14.2 |
| rubyonrails:rails | 0.14.3 |
| rubyonrails:rails | 0.14.4 |
| rubyonrails:rails | 1.0.0 |
| rubyonrails:rails | 1.1.0 |
| rubyonrails:rails | 1.1.1 |
| rubyonrails:rails | 1.1.2 |
| rubyonrails:rails | 1.1.3 |
| rubyonrails:ruby_on_rails | through 1.1.4 |
| rubyonrails:ruby_on_rails | 0.5.0 |
| rubyonrails:ruby_on_rails | 0.5.5 |
| rubyonrails:ruby_on_rails | 0.5.6 |
| rubyonrails:ruby_on_rails | 0.5.7 |
| rubyonrails:ruby_on_rails | 0.6.0 |
| rubyonrails:ruby_on_rails | 0.6.5 |
| rubyonrails:ruby_on_rails | 0.7.0 |
| rubyonrails:ruby_on_rails | 0.8.0 |
| rubyonrails:ruby_on_rails | 0.8.5 |
| rubyonrails:ruby_on_rails | 0.9.0 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-rvpq-5xqx-pfpp | RubyGems | rails | >=1.1.0 <1.1.6 | 1.1.6 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | rails | 1.1.5-1 | DEBIAN-CVE-2006-4111 |
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-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
- CAPEC-242 Code Injection Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
References
- http://blog.koehntopp.de/archives/1367-Ruby-On-Rails-Mandatory-Mystery-Patch.html
- http://weblog.rubyonrails.org/2006/8/9/rails-1-1-5-mandatory-security-patch-and-other-tidbits
- http://www.gentoo.org/security/en/glsa/glsa-200608-20.xml
- http://www.securityfocus.com/bid/19454
- http://secunia.com/advisories/21466
- http://secunia.com/advisories/21749
- http://www.vupen.com/english/advisories/2006/3237
- http://securitytracker.com/id?1016673
- http://www.novell.com/linux/security/advisories/2006_21_sr.html