CVE-2013-4164 is a heap-based buffer overflow in Ruby's conversion of strings to floating-point values. It affects Ruby 1.8; Ruby 1.9 releases before 1.9.3-p484; Ruby 2.0 releases before 2.0.0-p353; Ruby 2.1 releases before 2.1.0-preview2; and development trunk revisions before r43780. A crafted string supplied to floating-point conversion, including through String#to_f or JSON.parse, can corrupt heap memory.
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.
This repository contains a single Metasploit auxiliary module: 'modules/auxiliary/dos/http/rails_json_float_dos.rb'. The module targets a vulnerability in Ruby's floating point number parsing (CVE-2013-4164), which can be exploited via a Ruby on Rails application that processes JSON input. The exploit works by sending a specially crafted JSON array containing a very large floating point number as a string to the target endpoint (default '/'), causing a heap-based buffer overflow and crashing the Ruby process, resulting in a denial of service (DoS). The module allows customization of the HTTP verb and target URI. It is operational and has been tested against Ruby 1.9.3-p448 with WebRick and Thin web servers. The code is written in Ruby and is structured as a standard Metasploit auxiliary module, making use of the framework's HTTP client and DoS mixins. No hardcoded IPs or domains are present; the endpoint is user-supplied.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.