Xml Rpc: A security weakness

Xml Rpc is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 7.5 CVSS · secalert@redhat.com

NVD score 7.5 CVSS 2.0 · nvd@nist.gov

Component: Xml Rpc
Plugin slug: xmlrpc.php
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Jul 05, 2005
Weakness: CWE-94 — Improper Control of Generation of Code ('Code Injection')

This CVE was published Jul 05, 2005 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Xml Rpc to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

NVD vector: AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Update, patch or deactivate.

Technical description

Primary and upstream sources