CVE-2012-4915

Google Doc Embedder < 2.5.4 - Directory Traversal

2013-01-08 00:00
Charlie Eriksen

Strategic Overview

Status
Patched in 2.5.4
Affected Plugin
Google Doc Embedder
Affected Version
< 2.5.4
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2012-4915
View all Google Doc Embedder vulnerabilities

At a glance

CVE-2012-4915 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Google Doc Embedder WordPress plugin, affecting versions < 2.5.4. 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 2.5.4; sites on affected versions should update now. Disclosed January 2013, reported by Charlie Eriksen.

Vulnerability Overview

Directory traversal vulnerability in the Google Doc Embedder plugin before 2.5.4 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter to libs/pdf.php.

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 Google Doc Embedder < 2.5.4 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 Google Doc Embedder the fix is 2.5.4: builds < 2.5.4 are affected, anything from 2.5.4 onward is not.

Remediation

Update to version 2.5.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Google Doc Embedder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Google Doc Embedder 2.5.4 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