Overview 105 matches · 0 in Waratek scope · 0 protected · 8 exploited · 7 CISA KEV · 8 public PoC · 7 EPSS ≥ 0.5
105matches
0in Waratek scope0.0%
0protected0.0%
8exploited7.6%
7CISA KEV6.7%
8public PoC7.6%
7EPSS ≥ 0.56.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
2
1.9%
Not applicable
103
98.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
105
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 19 / year
20142
Not applicable2
Critical2
not blocked2
Exploited2
20155
Outside Waratek scope1
Not applicable4
High4
Medium1
not blocked5
Working exploit published1
No public exploit4
20160
20173
Not applicable3
Critical1
High2
not blocked3
Working exploit published1
No public exploit2
20183
Not applicable3
Critical1
High1
Medium1
not blocked3
Forecast only1
No public exploit2
20196
Not applicable6
High2
Medium4
not blocked6
No public exploit6
202018
Outside Waratek scope1
Not applicable17
Critical2
High8
Medium7
Low1
not blocked18
Working exploit published1
Forecast only1
No public exploit16
202119
Not applicable19
Critical2
High3
Medium8
Low6
not blocked19
Proof of concept only1
No public exploit18
202211
Not applicable11
Critical4
High3
Medium4
not blocked11
No public exploit11
202311
Not applicable11
Critical1
High8
Medium2
not blocked11
Proof of concept only2
No public exploit9
20247
Not applicable7
High5
Medium1
Low1
not blocked7
Exploited1
No public exploit6
202510
Not applicable10
Critical2
High6
Medium2
not blocked10
Proof of concept only2
No public exploit8
202610
Not applicable10
Critical3
High5
Medium2
not blocked10
Exploited5
No public exploit5
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2015-3214 | Medium | 2015-08-31 | Not applicable | Working exploit published | The pit_ioport_read in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read lengths and write lengths, which might allow guest OS users to execute arbitrary code on the host OS by triggering use of an invalid index. |
| CVE-2015-5165 | High | 2015-08-12 | Not applicable | No public exploit | The C+ mode offload emulation in the RTL8139 network card device model in QEMU, as used in Xen 4.5.x and earlier, allows remote attackers to read process heap memory via unspecified vectors. |
| CVE-2015-3209 | High | 2015-06-15 | Outside Waratek scope | No public exploit | Heap-based buffer overflow in the PCNET controller in QEMU allows remote attackers to execute arbitrary code by sending a packet with TXSTATUS_STARTPACKET set and then a crafted packet with TXSTATUS_DEVICEOWNS set. |
| CVE-2014-7169 | Critical | 2014-09-25 | Not applicable | Exploited | GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown other impact via a crafted environment, as demonstrated by vectors involving the ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules in the Apache HTTP Server, scripts executed by unspecified DHCP clients, and other situations in which setting the environment occurs across a privilege boundary from Bash execution. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-6271. |
| CVE-2014-6271 | Critical | 2014-09-24 | Not applicable | Exploited | GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by vectors involving the ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules in the Apache HTTP Server, scripts executed by unspecified DHCP clients, and other situations in which setting the environment occurs across a privilege boundary from Bash execution, aka "ShellShock." NOTE: the original fix for this issue was incorrect; CVE-2014-7169 has been assigned to cover the vulnerability that is still present after the incorrect fix. |