Ruby CVEs with no public exploit
4 CVEs
Overview 4 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
4matches
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
4
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
4
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
4
100.0%
split by
peak 2 / month
Dec 111
No exploit published1
Medium1
not blocked1
No public exploit1
Jan 120
Feb 120
Mar 120
Apr 120
May 120
Jun 120
Jul 120
Aug 120
Sep 120
Oct 120
Nov 122
No exploit published2
Medium2
not blocked2
No public exploit2
Dec 120
Jan 130
Feb 130
Mar 130
Apr 131
No exploit published1
Medium1
not blocked1
No public exploit1
Dec 11Feb 12Apr 12Jun 12Aug 12Oct 12Dec 12Feb 13Apr 13
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2013-1821 | Medium | 2013-04-09 | No exploit published | No public exploit | lib/rexml/text.rb in the REXML parser in Ruby before 1.9.3-p392 allows remote attackers to cause a denial of service (memory consumption and crash) via crafted text nodes in an XML document, aka an XML Entity Expansion (XEE) attack. |
| CVE-2012-5370 | Medium | 2012-11-28 | No exploit published | No public exploit | JRuby computes hash values without properly restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table, as demonstrated by a universal multicollision attack against the MurmurHash2 algorithm, a different vulnerability than CVE-2011-4838. |
| CVE-2010-1330 | Medium | 2012-11-23 | No exploit published | No public exploit | The regular expression engine in JRuby before 1.4.1, when $KCODE is set to 'u', does not properly handle characters immediately after a UTF-8 character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted string. |
| CVE-2011-5036 | Medium | 2011-12-30 | No exploit published | No public exploit | Rack before 1.1.3, 1.2.x before 1.2.5, and 1.3.x before 1.3.6 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters. |