Loading vulnerability…
CVE-2014-9016 is a vulnerability in the password hashing API of Drupal 7.x before 7.34 and the Secure Password Hashes (phpass) module 6.x-2.x before 6.x-2.1. The flaw allows remote attackers to trigger excessive CPU and memory consumption by submitting specially crafted requests, such as extremely long passwords, to the password hashing routines. This can result in a denial of service condition as the server resources are exhausted during the hash computation process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module: 'WordPress Long Password DoS'. The module targets WordPress installations prior to versions 3.7.5, 3.8.5, 3.9.3, and 4.0.1, exploiting CVE-2014-9016. The exploit works by sending a large number of HTTP POST requests to the WordPress login endpoint (/wp-login.php), each with an extremely long password. This triggers excessive CPU usage on the server due to inefficient password hashing, potentially resulting in a denial of service. The module allows configuration of the password length, number of requests, concurrency, and timeout. It can optionally validate the existence of a specified username before launching the attack. The code is written in Ruby and is designed to be run within the Metasploit framework. The main attack vector is network-based, targeting the HTTP login interface of WordPress. The only fingerprintable endpoint is the standard WordPress login path.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.