CVE-2017-1000434

furikake <= 0.1.0 - Open Redirect

2018-01-01 00:00
Carl Clegg

Strategic Overview

Status
Patched in 0.1.1
Affected Plugin
furikake
Affected Version
<= 0.1.0
CVSS
6.1Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2017-1000434
View all furikake vulnerabilities

At a glance

CVE-2017-1000434 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the furikake WordPress plugin, affecting versions <= 0.1.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.1.1; sites on affected versions should update now. Disclosed January 2018, reported by Carl Clegg.

Vulnerability Overview

Wordpress plugin Furikake version 0.1.0 is vulnerable to an Open Redirect The furikake-redirect parameter on a page allows for a redirect to an attacker controlled page classes/Furigana.php: header('location:'.urldecode($_GET['furikake-redirect']));

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.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

furikake <= 0.1.0 carries this weakness at furikake-redirect, and reaching it takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For furikake the fix is 0.1.1: builds <= 0.1.0 are affected, anything from 0.1.1 onward is not.

Remediation

Update to version 0.1.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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