Overview 8 matches · 5 in Waratek scope · 4 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
8matches
5in Waratek scope62.5%
4protected50.0%
0exploited0.0%
0CISA KEV0.0%
1public PoC12.5%
1EPSS ≥ 0.512.5%
Protected by Waratek
4
50.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
12.5%
Outside Waratek scope
0
0.0%
Not applicable
3
37.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
4
50.0%
partly blocked
0
0.0%
not blocked
4
50.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
12.5%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
7
87.5%
split by
peak 3 / year
20052
Not applicable2
High2
not blocked2
Working exploit published1
No public exploit1
20060
20070
20080
20090
20100
20110
20120
20130
20140
20150
20160
20173
Protected by Waratek2
No exploit published1
Critical1
High1
Medium1
blocked by ARMR today2
not blocked1
No public exploit3
20180
20190
20201
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
20211
Not applicable1
High1
not blocked1
No public exploit1
20220
20231
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
2005200720092011201320152017201920212023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-36641 | Critical | 2023-01-05 | Protected by Waratek | No public exploit | A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0. This vulnerability affects the function ResponseParser of the file src/main/java/de/timroes/axmlrpc/ResponseParser.java. The manipulation leads to xml external entity reference. Upgrading to version 1.14.0 is able to address this issue. The patch is identified as 456752ebc1ef4c0db980cb5b01a0b3cd0a9e0bae. It is recommended to upgrade the affected component. VDB-217450 is the identifier assigned to this vulnerability. |
| CVE-2021-24629 | High | 2021-11-08 | Not applicable | No public exploit | The Post Content XMLRPC WordPress plugin through 1.0 does not sanitise or escape multiple GET/POST parameters before using them in SQL statements in the admin dashboard, leading to an authenticated SQL Injections |
| CVE-2019-17570 | Critical | 2020-01-23 | Protected by Waratek | No public exploit | An untrusted deserialization was found in the org.apache.xmlrpc.parser.XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code. Apache XML-RPC is no longer maintained and this issue will not be fixed. |
| CVE-2016-5003 | Critical | 2017-10-27 | Protected by Waratek | No public exploit | The Apache XML-RPC (aka ws-xmlrpc) library 3.1.3, as used in Apache Archiva, allows remote attackers to execute arbitrary code via a crafted serialized Java object in an <ex:serializable> element. |
| CVE-2016-5002 | High | 2017-10-27 | Protected by Waratek | No public exploit | XML external entity (XXE) vulnerability in the Apache XML-RPC (aka ws-xmlrpc) library 3.1.3, as used in Apache Archiva, allows remote attackers to conduct server-side request forgery (SSRF) attacks via a crafted DTD. |
| CVE-2016-5004 | Medium | 2017-06-06 | No exploit published | No public exploit | The Content-Encoding HTTP header feature in ws-xmlrpc 3.1.3 as used in Apache Archiva allows remote attackers to cause a denial of service (resource consumption) by decompressing a large file containing zeroes. |
| CVE-2005-2498 | High | 2005-08-15 | Not applicable | No public exploit | Eval injection vulnerability in PHPXMLRPC 1.1.1 and earlier (PEAR XML-RPC for PHP), as used in multiple products including (1) Drupal, (2) phpAdsNew, (3) phpPgAds, and (4) phpgroupware, allows remote attackers to execute arbitrary PHP code via certain nested XML tags in a PHP document that should not be nested, which are injected into an eval function call, a different vulnerability than CVE-2005-1921. |
| CVE-2005-1921 | High | 2005-07-05 | Not applicable | Working exploit published | Eval injection vulnerability in PEAR XML_RPC 1.3.0 and earlier (aka XML-RPC or xmlrpc) and PHPXMLRPC (aka XML-RPC For PHP or php-xmlrpc) 1.1 and earlier, as used in products such as (1) WordPress, (2) Serendipity, (3) Drupal, (4) egroupware, (5) MailWatch, (6) TikiWiki, (7) phpWebSite, (8) Ampache, and others, allows remote attackers to execute arbitrary PHP code via an XML file, which is not properly sanitized before being used in an eval statement. |