CVE-2014-0166

WordPress Core < 3.8.2 - Authentication Cookie Forgery

2014-04-08 00:00
Jon Cave

Strategic Overview

Status
Patched in 3.7.2
Affected Core
WordPress 3.8
Affected Version
3.7 – 3.8.1 · 3 branches
CVSS
6.5Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2014-0166
View all WordPress 3.8 vulnerabilities

At a glance

CVE-2014-0166 is a medium-severity Improper Authentication vulnerability in the WordPress 3.8 WordPress release line, affecting 3.7 – 3.8.1 · 3 branches. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.2; sites on affected versions should update now. Disclosed April 2014, reported by Jon Cave.

Vulnerability Overview

The wp_validate_auth_cookie function in wp-includes/pluggable.php in WordPress before 3.7.2 and 3.8.x before 3.8.2 does not properly determine the validity of authentication cookies, which makes it easier for remote attackers to obtain access via a forged cookie.

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.

CWE-287: Improper Authentication

Reaching this weakness in WordPress 3.8 3.7 – 3.8.1 · 3 branches takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WordPress 3.8 the fix is 3.7.2: builds 3.7 – 3.8.1 · 3 branches are affected, anything from 3.7.2 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.2, 3.8.2

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: updating to 3.7.2 is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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