Overview 120 matches · 14 in Waratek scope · 6 protected · 3 exploited · 3 CISA KEV · 9 public PoC · 5 EPSS ≥ 0.5
120matches
14in Waratek scope11.7%
6protected5.0%
3exploited2.5%
3CISA KEV2.5%
9public PoC7.5%
5EPSS ≥ 0.54.2%
Protected by Waratek
6
5.0%
Rule in development
0
0.0%
Mitigation candidate
1
0.8%
No exploit published
7
5.8%
Outside Waratek scope
52
43.3%
Not applicable
54
45.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
6
5.0%
partly blocked
0
0.0%
not blocked
114
95.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
2.5%
Working exploit published
0
0.0%
Proof of concept only
19
15.8%
Forecast only
1
0.8%
No public exploit
97
80.8%
split by
peak 33 / year
20071
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
20080
20090
20100
20110
20120
20130
20140
20150
20161
Outside Waratek scope1
High1
not blocked1
Exploited1
20171
Not applicable1
Critical1
not blocked1
No public exploit1
20182
No exploit published2
Critical2
not blocked2
No public exploit2
201914
Outside Waratek scope14
Critical1
High9
Medium3
Low1
not blocked14
No public exploit14
202033
Protected by Waratek3
No exploit published2
Outside Waratek scope17
Not applicable11
Critical1
High13
Medium12
Low7
blocked by ARMR today3
not blocked30
Proof of concept only4
No public exploit29
202124
Protected by Waratek2
Outside Waratek scope9
Not applicable13
Critical2
High5
Medium17
blocked by ARMR today2
not blocked22
Exploited1
Proof of concept only3
Forecast only1
No public exploit19
202229
Protected by Waratek1
Mitigation candidate1
No exploit published3
Outside Waratek scope2
Not applicable22
Critical1
High15
Medium12
Low1
blocked by ARMR today1
not blocked28
Exploited1
Proof of concept only8
No public exploit20
20237
Outside Waratek scope2
Not applicable5
Critical5
High2
not blocked7
Proof of concept only1
No public exploit6
20245
Outside Waratek scope5
Critical2
High2
Medium1
not blocked5
Proof of concept only1
No public exploit4
20253
Outside Waratek scope1
Not applicable2
High1
Medium1
Low1
not blocked3
Proof of concept only2
No public exploit1
2007200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-5188 | High | 2020-01-08 | Outside Waratek scope | No public exploit | A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. |
| CVE-2019-19462 | Medium | 2019-11-30 | Outside Waratek scope | No public exploit | relay_open in kernel/relay.c in the Linux kernel through 5.4.1 allows local users to cause a denial of service (such as relay blockage) by triggering a NULL alloc_percpu result. |
| CVE-2019-19069 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the fastrpc_dma_buf_attach() function in drivers/misc/fastrpc.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering dma_get_sgtable() failures, aka CID-fc739a058d99. |
| CVE-2019-19063 | Medium | 2019-11-18 | Outside Waratek scope | No public exploit | Two memory leaks in the rtl_usb_probe() function in drivers/net/wireless/realtek/rtlwifi/usb.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption), aka CID-3f9361695113. |
| CVE-2019-19061 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the adis_update_scan_mode_burst() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-9c0530e898f3. |
| CVE-2019-19060 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the adis_update_scan_mode() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-ab612b1daf41. |
| CVE-2019-19057 | Low | 2019-11-18 | Outside Waratek scope | No public exploit | Two memory leaks in the mwifiex_pcie_init_evt_ring() function in drivers/net/wireless/marvell/mwifiex/pcie.c in the Linux kernel through 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering mwifiex_map_pci_memory() failures, aka CID-d10dcb615c8e. |
| CVE-2019-19054 | Medium | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the cx23888_ir_probe() function in drivers/media/pci/cx23885/cx23888-ir.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering kfifo_alloc() failures, aka CID-a7b2df76b42b. |
| CVE-2019-19053 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the rpmsg_eptdev_write_iter() function in drivers/rpmsg/rpmsg_char.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering copy_from_iter_full() failures, aka CID-bbe692e349e2. |
| CVE-2019-19052 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the gs_can_open() function in drivers/net/can/usb/gs_usb.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering usb_submit_urb() failures, aka CID-fb5be6a7b486. |
| CVE-2019-19050 | High | 2019-11-18 | Outside Waratek scope | No public exploit | A memory leak in the crypto_reportstat() function in crypto/crypto_user_stat.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_reportstat_alg() failures, aka CID-c03b04dcdba1. |
| CVE-2019-19044 | High | 2019-11-18 | Outside Waratek scope | No public exploit | Two memory leaks in the v3d_submit_cl_ioctl() function in drivers/gpu/drm/v3d/v3d_gem.c in the Linux kernel before 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering kcalloc() or v3d_job_init() failures, aka CID-29cd13cfd762. |
| CVE-2019-18805 | Critical | 2019-11-07 | Outside Waratek scope | No public exploit | An issue was discovered in net/ipv4/sysctl_net_ipv4.c in the Linux kernel before 5.0.11. There is a net/ipv4/tcp_input.c signed integer overflow in tcp_ack_update_rtt() when userspace writes a very large integer to /proc/sys/net/ipv4/tcp_min_rtt_wlen, leading to a denial of service or possibly unspecified other impact, aka CID-19fad20d15a6. |
| CVE-2019-11815 | High | 2019-05-08 | Outside Waratek scope | No public exploit | An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux kernel before 5.0.8. There is a race condition leading to a use-after-free, related to net namespace cleanup. |
| CVE-2018-20836 | High | 2019-05-07 | Outside Waratek scope | No public exploit | An issue was discovered in the Linux kernel before 4.20. There is a race condition in smp_task_timedout() and smp_task_done() in drivers/scsi/libsas/sas_expander.c, leading to a use-after-free. |
| CVE-2017-7658 | Critical | 2018-06-26 | No exploit published | No public exploit | In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing authorization, the fake pipelined request would bypass that authorization. |
| CVE-2017-7657 | Critical | 2018-06-26 | No exploit published | No public exploit | In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty was deployed behind an intermediary that imposed some authorization and that intermediary allowed arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the intermediary as a request. |
| CVE-2016-9841 | Critical | 2017-05-23 | Not applicable | No public exploit | inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic. |
| CVE-2016-5195 | High | 2016-11-10 | Outside Waratek scope | Exploited | Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect handling of a copy-on-write (COW) feature to write to a read-only memory mapping, as exploited in the wild in October 2016, aka "Dirty COW." |
| CVE-2007-2768 | Medium | 2007-05-21 | Outside Waratek scope | No public exploit | OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243. |