Overview 5 matches · 0 protected · 2 exploited · 0 CISA KEV · 3 public PoC
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
3
60.0%
No exploit published
2
40.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
5
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
40.0%
Working exploit published
1
20.0%
Proof of concept only
0
0.0%
Forecast only
2
40.0%
No public exploit
0
0.0%
split by
peak 3 / month
Apr 191
Mitigation candidate1
Medium1
not blocked1
Exploited1
May 190
Jun 190
Jul 190
Aug 190
Sep 191
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
Oct 190
Nov 190
Dec 190
Jan 200
Feb 200
Mar 200
Apr 203
Mitigation candidate1
No exploit published2
Medium3
not blocked3
Exploited1
Forecast only2
Apr 19Jun 19Aug 19Oct 19Dec 19Feb 20Apr 20
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-11022 | Medium | 2020-04-29 | Mitigation candidate | Exploited | In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-1927 | Medium | 2020-04-02 | No exploit published | Forecast only | In Apache HTTP Server 2.4.0 to 2.4.41, redirects configured with mod_rewrite that were intended to be self-referential might be fooled by encoded newlines and redirect instead to an an unexpected URL within the request URL. |
| CVE-2020-1934 | Medium | 2020-04-01 | No exploit published | Forecast only | In Apache HTTP Server 2.4.0 to 2.4.41, mod_proxy_ftp may use uninitialized memory when proxying to a malicious FTP server. |
| CVE-2019-10092 | Medium | 2019-09-26 | Mitigation candidate | Working exploit published | In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could cause the link on the error page to be malformed and instead point to a page of their choice. This would only be exploitable where a server was set up with proxying enabled but was misconfigured in such a way that the Proxy Error page was displayed. |
| CVE-2019-11358 | Medium | 2019-04-20 | Mitigation candidate | Exploited | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |