activerecord/lib/active_record/relation/query_methods.rb in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows
activerecord/lib/active_record/relation/query_methods.rb in Active Record in Ruby on Rails 4.0.x before 4.0.9 and 4.1.x before 4.1.5 allows remote attackers to bypass the strong parameters protection mechanism via crafted input to an application that makes create_with calls.
- Published
- Aug 20, 2014
- Updated
- Jun 16, 2026
- EPSS
- 2.8% · 86th percentile
- CWE
- CWE-264
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.8%
Affected systems
| 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 rails4.0.0
- rubyonrails rails4.0.1
- rubyonrails rails4.0.2
- rubyonrails rails4.0.3
- rubyonrails rails4.0.4
- rubyonrails rails4.0.5
- rubyonrails rails4.0.6
- rubyonrails rails4.0.7
- rubyonrails rails4.0.8
- rubyonrails rails4.1.0
- rubyonrails rails4.1.1
- rubyonrails rails4.1.2
- rubyonrails rails4.1.3
- rubyonrails rails4.1.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:4.1.5-1 | 2:4.1.5-1 |
| openSUSE:Tumbleweed | rubygem-railties-4_2 | before 5.0.0.1-1.1 | 5.0.0.1-1.1 |
| Red Hat:rhel_software_collections:1::el6 | ror40-rubygem-activerecord | before 1:4.0.2-2.3.el6 | 1:4.0.2-2.3.el6 |
| Red Hat:rhel_software_collections:1::el6 | ror40-rubygem-activerecord-doc | before 1:4.0.2-2.3.el6 | 1:4.0.2-2.3.el6 |
| Red Hat:rhel_software_collections:1::el7 | ror40-rubygem-activerecord | before 1:4.0.2-2.3.el7 | 1:4.0.2-2.3.el7 |
| Red Hat:rhel_software_collections:1::el7 | ror40-rubygem-activerecord-doc | before 1:4.0.2-2.3.el7 | 1:4.0.2-2.3.el7 |
| RubyGems | activerecord | from 4.0.0 · before 4.0.9 | 4.0.9 |
| RubyGems | activerecord | from 4.1.0 · before 4.1.5 | 4.1.5 |
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 accepKEV90Now
- 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, anKEV89Now
- 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 gene66This week
- CVE-2020-8163The is a code injection vulnerability in versions of Rails prior to 5.0.1 that wouldallow an attacker who controlled the `locals` argument o60This week
- CVE-2013-0156active_support/core_ext/hash/conversions.rb in Ruby on Rails before 2.3.15, 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.160This week
- CVE-2013-0333lib/active_support/json/backends/yaml.rb in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to59Plan
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:4.1.5-1 · Debian:12 | Package registry (OSV) |
| opensuse:rubygem-railties-4_2 | 5.0.0.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:ror40-rubygem-activerecord | 1:4.0.2-2.3.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| red hat:ror40-rubygem-activerecord-doc | 1:4.0.2-2.3.el6 · Red Hat:rhel_software_collections:1::el6 | Package registry (OSV) |
| RubyGems:activerecord | 4.0.9 | Package registry (OSV) |
| RubyGems:activerecord | 4.1.5 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
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
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- openwall.com/lists/oss-security/2014/08/18/10
- rhn.redhat.com/errata/RHSA-2014-1102.html
- secunia.com/advisories/60347
- groups.google.com/forum/message/raw?msg=rubyonrails-security/M4chq5Sb540/CC1Fh0Y_NWwJ
Vendor advisories and official records. Exploit/PoC links are deliberately left out.