Description: ------------ If a client calls an RPC method but supplies a parameter count that does not match any of the method's signatures as defined in the dispatch map, the function verifySignature() of XML_RPC_Server will cause PHP undefined variable notices if PHP notices have not been disabled. This is a security issue because it exposes the script path to the client. Also, having the server's XML response prepended with PHP notices will cause many clients to reject the return payload as invalid during parsing. Reproduce code: --------------- Build the example server and client from the end-user documentation. The built-in RPC method system.methodHelp() takes one parameter. Use the client to call this method with no parameters, and again with two or more parameters. Observe the response payload. Expected result: ---------------- A valid response from the server with a fault code of 3 and a fault string similar to "Bad parameter count". Actual result: -------------- Undefined variable notices occur for $wanted, $got, and $pno in the function verifySignature() of XML_RPC_Server. These will be prepended to the XML returned from the server, resulting in XML_RPC_Client to report its own fault code 2 (invalud return payload). Although the XML from the server does contain a faultCode and faultString, most other clients react similarly and reject the return payload during parsing. Fix ---- In the class XML_RPC_Server, replace the last line of the function verifySignature(). Before: return array(0, "Wanted ${wanted}, got ${got} at param ${pno})"); Fixed: if (isset($pno)) { return array(0, "Wanted ${wanted}, got ${got} at param ${pno})"); } else { return array(0, 'Bad parameter count'); }

Please see the reproduce code here: http://www.mikenaberezny.com/pear/bugs/4231

I have reopened this bug because the patch in 1.3.0RC2 has the side-effect of breaking support for optional method parameters. Please see a description and reproduce code here: http://www.mikenaberezny.com/pear/bugs/4231-addendum