Process crash via String-to-Float buffer over-read
Published May 9, 2022 · Updated Nov 4, 2025
Buffer over-read in affected Ruby releases allows attackers to crash processes through crafted String-to-Float conversions. An undisclosed internal conversion function reads beyond its buffer when Kernel#Float or String#to_f processes a crafted string. Reachability requires an application to pass attacker-controlled text into an affected conversion path; the result is usually a segmentation fault and, in limited circumstances, an illegal memory read.
Summary
What happened
Buffer over-read in affected Ruby releases allows attackers to crash processes through crafted String-to-Float conversions. An undisclosed internal conversion function reads beyond its buffer when Kernel#Float or String#to_f processes a crafted string. Reachability requires an application to pass attacker-controlled text into an affected conversion path; the result is usually a segmentation fault and, in limited circumstances, an illegal memory read.
The record
- CVE
- CVE-2022-28739
- Published
- May 9, 2022
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2022CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo