Overview 108 matches · 19 protected · 4 exploited · 1 CISA KEV · 7 public PoC · 8 EPSS ≥ 0.5
Protected by Waratek
19
17.6%
Rule in development
0
0.0%
Mitigation candidate
5
4.6%
No exploit published
84
77.8%
blocked by ARMR today
19
17.6%
partly blocked
0
0.0%
not blocked
89
82.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 20 / year
20161
Mitigation candidate1
High1
not blocked1
Working exploit published1
20172
Mitigation candidate1
No exploit published1
Critical1
High1
not blocked2
Exploited1
No public exploit1
201814
Protected by Waratek6
No exploit published8
Critical5
High6
Medium3
blocked by ARMR today6
not blocked8
No public exploit14
201920
Protected by Waratek1
No exploit published19
Critical5
High9
Medium6
blocked by ARMR today1
not blocked19
No public exploit20
20207
Protected by Waratek1
Mitigation candidate1
No exploit published5
Critical3
High2
Medium2
blocked by ARMR today1
not blocked6
Working exploit published1
No public exploit6
202114
Protected by Waratek3
Mitigation candidate1
No exploit published10
Critical2
High2
Medium8
Low2
blocked by ARMR today3
not blocked11
Exploited2
Working exploit published2
Forecast only2
No public exploit8
202213
Protected by Waratek3
No exploit published10
Critical1
High5
Medium6
Low1
blocked by ARMR today3
not blocked10
No public exploit13
202318
Protected by Waratek4
Mitigation candidate1
No exploit published13
Critical3
High6
Medium8
Low1
blocked by ARMR today4
not blocked14
Exploited1
Proof of concept only2
No public exploit15
202415
No exploit published15
High5
Medium10
not blocked15
Proof of concept only3
No public exploit12
20254
Protected by Waratek1
No exploit published3
High3
Medium1
blocked by ARMR today1
not blocked3
Proof of concept only1
No public exploit3
2016201720182019202020212022202320242025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-12536 | Medium | 2018-06-27 | No exploit published | No public exploit | In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system. |
| 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-2017-7656 | High | 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), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response. |
| CVE-2018-12538 | High | 2018-06-22 | No exploit published | No public exploit | In Eclipse Jetty versions 9.4.0 through 9.4.8, when using the optional Jetty provided FileSessionDataStore for persistent storage of HttpSession details, it is possible for a malicious user to access/hijack other HttpSessions and even delete unmatched HttpSessions present in the FileSystem's storage for the FileSessionDataStore. |
| CVE-2017-9735 | High | 2017-06-16 | No exploit published | No public exploit | Jetty through 9.4.x is prone to a timing channel in util/security/Password.java, which makes it easier for remote attackers to obtain access by observing elapsed times before rejection of incorrect passwords. |
| CVE-2016-4800 | Critical | 2017-04-13 | Mitigation candidate | Exploited | The path normalization mechanism in PathResource class in Eclipse Jetty 9.3.x before 9.3.9 on Windows allows remote attackers to bypass protected resource restrictions and other security constraints via a URL with certain escaped characters, related to backslashes. |
| CVE-2015-2080 | High | 2016-10-07 | Mitigation candidate | Working exploit published | The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process memory via illegal characters in an HTTP header, aka JetLeak. |