Download Manager <= 2.8.7 - Missing Authorization

2016-01-19 00:00
James Golovich

Strategic Overview

Status
Patched in 2.8.8
Affected Plugin
Download Manager
Affected Version
< 2.8.8
CVSS
9.1Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Download Manager vulnerabilities

At a glance

This record tracks a critical-severity Missing Authorization vulnerability in the Download Manager WordPress plugin, affecting versions < 2.8.8. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.8.8; sites on affected versions should update now. Disclosed January 2016, reported by James Golovich.

Vulnerability Overview

The Download Manager plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the savePackage() function in versions up to, and including, 2.8.7. This makes it possible for unauthenticated attackers to associate arbitrary files with posts and subsequently download those files causing sensitive information disclosure.

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, integrity.

CWE-862: Missing Authorization

Download Manager < 2.8.8 carries this weakness at savePackage(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Download Manager the fix is 2.8.8: builds < 2.8.8 are affected, anything from 2.8.8 onward is not.

Remediation

Update to version 2.8.8, or a newer patched version

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: Download Manager 2.8.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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