CVE-2022-28739
N/A
N/A
Summary
There is a buffer over-read in Ruby before 2.6.10, 2.7.x before 2.7.6, 3.x before 3.0.4, and 3.1.x before 3.1.2. It occurs in String-to-Float conversion, including Kernel#Float and String#to_f.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| n/a | n/a | n/a | affected |
Weaknesses
- n/a
ADP Enrichment
CVE Program Container
Additional References
- https://hackerone.com/reports/1248108
- https://security-tracker.debian.org/tracker/CVE-2022-28739
- https://www.ruby-lang.org/en/news/2022/04/12/buffer-overrun-in-string-to-float-cve-2022-28739/
- https://security.netapp.com/advisory/ntap-20220624-0002/
- https://support.apple.com/kb/HT213488
- https://support.apple.com/kb/HT213494
- https://support.apple.com/kb/HT213493
- http://seclists.org/fulldisclosure/2022/Oct/41
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/30
- http://seclists.org/fulldisclosure/2022/Oct/29
- http://seclists.org/fulldisclosure/2022/Oct/42
- https://lists.debian.org/debian-lts-announce/2023/06/msg00012.html
- https://security.gentoo.org/glsa/202401-27
- https://lists.debian.org/debian-lts-announce/2024/09/msg00000.html
References
- https://hackerone.com/reports/1248108
- https://security-tracker.debian.org/tracker/CVE-2022-28739
- https://www.ruby-lang.org/en/news/2022/04/12/buffer-overrun-in-string-to-float-cve-2022-28739/
- https://security.netapp.com/advisory/ntap-20220624-0002/
- https://support.apple.com/kb/HT213488
- https://support.apple.com/kb/HT213494
- https://support.apple.com/kb/HT213493
- http://seclists.org/fulldisclosure/2022/Oct/41
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/30
- http://seclists.org/fulldisclosure/2022/Oct/29
- http://seclists.org/fulldisclosure/2022/Oct/42
- https://lists.debian.org/debian-lts-announce/2023/06/msg00012.html
- https://security.gentoo.org/glsa/202401-27
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.