Overview 3 matches · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
3
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
blocked by ARMR today
3
100.0%
partly blocked
0
0.0%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
1
33.3%
Forecast only
0
0.0%
No public exploit
2
66.7%
split by
peak 2 / month
Feb 182
Protected by Waratek2
Critical2
blocked by ARMR today2
Proof of concept only1
No public exploit1
Mar 180
Apr 180
May 180
Jun 180
Jul 180
Aug 180
Sep 180
Oct 180
Nov 180
Dec 180
Jan 190
Feb 190
Mar 190
Apr 190
May 190
Jun 190
Jul 191
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Mar 18May 18Jul 18Sep 18Nov 18Jan 19Mar 19May 19Jul 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-11307 | Critical | 2019-07-09 | Protected by Waratek | No public exploit | An issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.5. Use of Jackson default typing along with a gadget class from iBatis allows exfiltration of content. Fixed in 2.7.9.4, 2.8.11.2, and 2.9.6. |
| CVE-2017-7525 | Critical | 2018-02-06 | Protected by Waratek | Proof of concept only | A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. |
| CVE-2017-15095 | Critical | 2018-02-06 | Protected by Waratek | No public exploit | A deserialization flaw was discovered in the jackson-databind in versions before 2.8.10 and 2.9.1, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525 by blacklisting more classes that could be used maliciously. |