lib/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 to
Noroxi assessment
Priority: Plan (action score 59/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 95.5% (FIRST EPSS); higher than 99.8% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: rails (Debian:12) 2.3.14.1; rails (Debian:6.0) 2.3.5-1.2+squeeze6; rubygem-activesupport (Red Hat:openshift:1::el6) 1:3.0.13-4.el6op.
Add it to your regular patch cycle. Upgrade to rails (Debian:12) 2.3.14.1; rails (Debian:6.0) 2.3.5-1.2+squeeze6; rubygem-activesupport (Red Hat:openshift:1::el6) 1:3.0.13-4.el6op 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
lib/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 to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156.
- Published
- Jan 30, 2013
- Updated
- Jun 16, 2026
- EPSS
- 95.5% · 99th percentile
- CWE
- —
Report tools
Action score
59
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 29 / 30 · 95.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| rubyonrails | ruby on rails | cpe:2.3:a:rubyonrails:ruby_on_rails |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rubyonrails rails2.3.0
- rubyonrails rails2.3.1
- rubyonrails rails2.3.10
- rubyonrails rails2.3.11
- rubyonrails rails2.3.12
- rubyonrails rails2.3.13
- rubyonrails rails2.3.14
- rubyonrails rails2.3.15
- rubyonrails rails2.3.2
- rubyonrails rails2.3.3
- rubyonrails rails2.3.4
- rubyonrails rails2.3.9
- rubyonrails rails3.0.0
- rubyonrails rails3.0.1
- rubyonrails rails3.0.10
- rubyonrails rails3.0.11
- rubyonrails rails3.0.12
- rubyonrails rails3.0.13
- rubyonrails rails3.0.14
- rubyonrails rails3.0.16
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.14.1 | 2.3.14.1 |
| Debian:6.0 | rails | before 2.3.5-1.2+squeeze6 | 2.3.5-1.2+squeeze6 |
| Red Hat:openshift:1::el6 | rubygem-activesupport | before 1:3.0.13-4.el6op | 1:3.0.13-4.el6op |
| RubyGems | activesupport | from 2.3.2 · before 2.3.16 | 2.3.16 |
| RubyGems | activesupport | from 3.0.0 · before 3.0.20 | 3.0.20 |
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
Published before and after this one in the same product
- ← EarlierCVE-2013-0155Jan 13, 2013 · Ruby on Rails 3.0.x before 3.0.19, 3.1.x before 3.1.10, and 3.2.x before 3.2.11 does not properly consider differences in parameter handling27Monitor
- ← EarlierCVE-2013-0156Jan 13, 2013 · active_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
- Later →CVE-2013-0276Feb 12, 2013 · ActiveRecord in Ruby on Rails before 2.3.17, 3.1.x before 3.1.11, and 3.2.x before 3.2.12 allows remote attackers to bypass the attr_protect18Monitor
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.14.1 · Debian:12 | Package registry (OSV) |
| red hat:rubygem-activesupport | 1:3.0.13-4.el6op · Red Hat:openshift:1::el6 | Package registry (OSV) |
| RubyGems:activesupport | 2.3.16 | Package registry (OSV) |
| RubyGems:activesupport | 3.0.20 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×2
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2013-01-29 |
| Metasploit module | auxiliary/scanner/http/rails_json_yaml_scannerRuby on Rails JSON Processor YAML Deserialization Scannerauxiliary | — |
| Metasploit module | exploit/multi/http/rails_json_yaml_code_execRuby on Rails JSON Processor YAML Deserialization Code Executionexploit | 2013-01-28 |
| Proof-of-concept repository on GitHub | stars:2 | 2013-01-29 |
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.
- Metasploit-2 d
- First PoC-1 d
- Published
- TodayOct 21, 2026+5012 d
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)
—
CVSS 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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- lists.apple.com/archives/security-announce/2013/Mar/msg00002.html
- rhn.redhat.com/errata/RHSA-2013-0201.html
- rhn.redhat.com/errata/RHSA-2013-0202.html
- rhn.redhat.com/errata/RHSA-2013-0203.html
- support.apple.com/kb/HT5784
- weblog.rubyonrails.org/2013/1/28/Rails-3-0-20-and-2-3-16-have-been-released/
- www.debian.org/security/2013/dsa-2613
- www.kb.cert.org/vuls/id/628463
- groups.google.com/group/rubyonrails-security/msg/52179af76915e518?dmode=source&output=gplain
- puppet.com/security/cve/cve-2013-0333
Vendor advisories and official records. Exploit/PoC links are deliberately left out.