CVE-2018-1000504

Redirection <= 2.7.3 - Local File Inclusion

2018-07-12 00:00
Glyn Wintle

Strategic Overview

Status
Patched in 2.8
Affected Plugin
Redirection
Affected Version
<= 2.7.3
CVSS
7.2High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2018-1000504
View all Redirection vulnerabilities

At a glance

CVE-2018-1000504 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Redirection WordPress plugin, affecting versions <= 2.7.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.8; sites on affected versions should update now. Disclosed July 2018, reported by Glyn Wintle.

Vulnerability Overview

Redirection version 2.7.3 contains a ACE via file inclusion vulnerability in Pass-through mode that can result in allows admins to execute any PHP file in the filesystem. This attack appear to be exploitable via Attacker must be have access to an admin account on the target site. This vulnerability appears to have been fixed in 2.8.

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-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Reaching this weakness in Redirection <= 2.7.3 takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Redirection the fix is 2.8: builds <= 2.7.3 are affected, anything from 2.8 onward is not.

Remediation

Update to version 2.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Redirection: 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: Redirection 2.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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