CVE-2013-7240

Advanced Dewplayer < 1.3 - Directory Traversal

2013-12-30 00:00
Henri Salo (fgeek)

Strategic Overview

Status
Patched in 1.3
Affected Plugin
Advanced Dewplayer
Affected Version
<= 1.2
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2013-7240
View all Advanced Dewplayer vulnerabilities

At a glance

CVE-2013-7240 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Advanced Dewplayer WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.3; sites on affected versions should update now. Disclosed December 2013, reported by Henri Salo (fgeek).

Vulnerability Overview

Directory traversal vulnerability in download-file.php in the Advanced Dewplayer plugin 1.2 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the dew_file parameter.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Advanced Dewplayer <= 1.2 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Advanced Dewplayer the fix is 1.3: builds <= 1.2 are affected, anything from 1.3 onward is not.

Remediation

Update to version 1.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Advanced Dewplayer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced Dewplayer 1.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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