This occurs in Lib/DocXMLRPCServer.py in Python 2.x, and in Lib/xmlrpc/server.py in Python 3.x. The documentation XML-RPC server in Python through 2.7.16, 3.x through 3.6.9, and 3.7.x through 3.7.4 has XSS via the server_title field. Apache XML-RPC is no longer maintained and this issue will not be fixed. A malicious XML-RPC server could target a XML-RPC client causing it to execute arbitrary code. This vulnerability was addressed in version 4.2.0.Īn untrusted deserialization was found in the .XmlRpcResponseParser:addResult method of Apache XML-RPC (aka ws-xmlrpc) library. It is possible, although unconfirmed, that the vulnerability has been used by some attackers in order to gain access to some Revive Adserver instances and deliver malware through them to third party websites. exploit serialize-related PHP vulnerabilities or PHP object injection. Such vulnerability could be used to perform various types of attacks, e.g. WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC.Īn attacker could send a specifically crafted payload to the XML-RPC invocation script and trigger the unserialize() call on the "what" parameter in the "openads.spc" RPC method. Wp-includes/class-wp-xmlrpc-server.php in WordPress before 5.5.2 allows attackers to gain privileges by using XML-RPC to comment on a post. XML-RPC request are vulnerable to unsafe deserialization and Cross-Site Scripting issues in Apache OFBiz 17.12.03 Note that this required site administrator access or access to the keypair. In JetBrains TeamCity before 2021.2, blind SSRF via an XML-RPC call was possible.Īn SQL injection risk existed on sites with MNet enabled and configured, via an XML-RPC call from the connected peer host.
#BUGZILLA XML RPC REGISTRATION#
JetBrains TeamCity before 2021.2 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registration via XML-RPC.
In JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCity server. An unauthenticated user can send a crafted XML-RPC message to consume all the resources of the server. The issue and the workaround are described in detail here.An XML Entity Expansion (XEE) issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. To fix it, make the type_id attribute #IMPLIED (optional) in the bugzilla.dtd file. This happens because the generated XML does not correspond to the bundled bugzilla.dtd.
#BUGZILLA XML RPC PASSWORD#
If the username and password are specified, you need to have Bugzilla XML-RPC interface switched on. The most common case seems to be #(\d+) - this will extract 1234 as issue ID from text "Fix for #1234".
The matched text (or the first group if there are groups defined) is used as the issue number. When enabling issue tracker integration in addition to general settings, you need to specify which strings are to be recognized as references to issues in your tracker.įor Bugzilla, you need to specify the Issue Id Pattern: a Java Regular Expression pattern to find the issue ID in the text.
0 kommentar(er)
