Overview 104 matches · 24 protected · 3 exploited · 2 CISA KEV · 8 public PoC · 5 EPSS ≥ 0.5
Protected by Waratek
24
23.1%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
78
75.0%
blocked by ARMR today
24
23.1%
partly blocked
0
0.0%
not blocked
80
76.9%
not established
0
0.0%
unrecorded
0
0.0%
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-1000142 | High | 2018-04-05 | No exploit published | No public exploit | An exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin version 1.39.0 and older in GhprbCause.java that allows an attacker with local file system access to obtain GitHub credentials. |
| CVE-2018-6660 | Medium | 2018-04-02 | Protected by Waratek | No public exploit | Directory Traversal vulnerability in McAfee ePolicy Orchestrator (ePO) 5.3.2, 5.3.1, 5.3.0 and 5.9.0 allows administrators to use Windows alternate data streams, which could be used to bypass the file extensions, via not properly validating the path when exporting a particular XML file. |
| CVE-2018-6659 | Medium | 2018-04-02 | No exploit published | No public exploit | Reflected Cross-Site Scripting vulnerability in McAfee ePolicy Orchestrator (ePO) 5.3.2, 5.3.1, 5.3.0 and 5.9.0 allows remote authenticated users to exploit an XSS issue via not sanitizing the user input. |
| CVE-2018-1295 | Critical | 2018-04-02 | Protected by Waratek | No public exploit | In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer. |