Loading vulnerability…
CVE-2013-0333 affects 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. The flaw is caused by improper conversion of JSON data into YAML before handing it to a YAML parser. Because the resulting data can trigger unsafe YAML decoding semantics, a remote attacker can supply crafted input that is deserialized in an unsafe manner. According to the provided advisory and description, successful exploitation can lead to arbitrary code execution, SQL injection, authentication bypass, and potentially denial of service. This issue is distinct from CVE-2013-0156.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module: 'rails_json_yaml_code_exec.rb', which exploits a remote code execution vulnerability (CVE-2013-0333) in the JSON processor of Ruby on Rails applications. The exploit works by sending a specially crafted JSON request containing a malicious YAML payload to the target Rails application's HTTP endpoint. The module supports both Rails 2 and Rails 3, and the payload is base64-encoded Ruby code that is executed upon deserialization. The exploit is operational and allows the attacker to execute arbitrary Ruby code, typically resulting in a shell or Meterpreter session. The main configurable endpoint is the TARGETURI, which specifies the path to the vulnerable application. The module is designed for use within the Metasploit framework and leverages its payload system for flexible post-exploitation capabilities.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.