Overview 5 matches · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
2
40.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
60.0%
blocked by ARMR today
2
40.0%
partly blocked
0
0.0%
not blocked
3
60.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
5
100.0%
split by
peak 1 / month
Jan 181
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
Feb 180
Mar 181
No exploit published1
High1
not blocked1
No public exploit1
Apr 180
May 181
No exploit published1
Critical1
not blocked1
No public exploit1
Jun 180
Jul 181
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
Aug 180
Sep 181
No exploit published1
Medium1
not blocked1
No public exploit1
Jan 18Feb 18Mar 18Apr 18May 18Jun 18Jul 18Aug 18Sep 18
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-14627 | Medium | 2018-09-04 | No exploit published | No public exploit | The IIOP OpenJDK Subsystem in WildFly before version 14.0.0 does not honour configuration when SSL transport is required. Servers before this version that are configured with the following setting allow clients to create plaintext connections: <transport-config confidentiality="required" trust-in-target="supported"/> |
| CVE-2018-10862 | Medium | 2018-07-27 | Protected by Waratek | No public exploit | WildFly Core before version 6.0.0.Alpha3 does not properly validate file paths in .war archives, allowing for the extraction of crafted .war archives to overwrite arbitrary files. This is an instance of the 'Zip Slip' vulnerability. |
| CVE-2018-10683 | Critical | 2018-05-09 | No exploit published | No public exploit | An issue was discovered in WildFly 10.1.2.Final. In the case of a default installation without a security realm reference, an attacker can successfully access the server without authentication. NOTE: the Security Realms documentation in the product's Admin Guide indicates that "without a security realm reference" implies "effectively unsecured." The vendor explicitly supports these unsecured configurations because they have valid use cases during development |
| CVE-2016-9589 | High | 2018-03-12 | No exploit published | No public exploit | Undertow in Red Hat wildfly before version 11.0.0.Beta1 is vulnerable to a resource exhaustion resulting in a denial of service. Undertow keeps a cache of seen HTTP headers in persistent connections. It was found that this cache can easily exploited to fill memory with garbage, up to "max-headers" (default 200) * "max-header-size" (default 1MB) per active TCP connection. |
| CVE-2018-1047 | Medium | 2018-01-24 | Protected by Waratek | No public exploit | A flaw was found in Wildfly 9.x. A path traversal vulnerability through the org.wildfly.extension.undertow.deployment.ServletResourceManager.getResource method could lead to information disclosure of arbitrary local files. |