CVE-2009-4140

Various Affected Software (Various Versions) - Arbitrary File Upload

2009-10-21 00:00
Anonymous

Strategic Overview

Status
Patched in 1.4.3.2
Affected Version
<= 1.4.3.1
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2009-4140
View all Woopra Analytics Plugin vulnerabilities

At a glance

CVE-2009-4140 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Woopra Analytics Plugin WordPress plugin, affecting versions <= 1.4.3.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.4.3.2; sites on affected versions should update now. Disclosed October 2009.

Vulnerability Overview

Unrestricted file upload vulnerability in ofc_upload_image.php in Open Flash Chart v2 Beta 1 through v2 Lug Wyrm Charmer, as used in Piwik 0.2.35 through 0.4.3, Woopra Analytics Plugin before 1.4.3.2, and possibly other products, when register_globals is enabled, allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension through the name parameter with the code in the HTTP_RAW_POST_DATA parameter, then accessing it via a direct request to the file in tmp-upload-images/.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in Woopra Analytics Plugin <= 1.4.3.1 takes a caller who can reach the endpoint. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Woopra Analytics Plugin the fix is 1.4.3.2: builds <= 1.4.3.1 are affected, anything from 1.4.3.2 onward is not.

Remediation

Update to version 1.4.3.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Woopra Analytics Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Woopra Analytics Plugin 1.4.3.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Other vulnerabilities in Woopra Analytics Plugin

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C