WordPress RokBox <= 2.13 - Denial of Service
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WordPress RokBox
- Affected Version
<= 2.13- CVSS
- 7.5High
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE pending
At a glance
This record tracks a high-severity Uncontrolled Resource Consumption vulnerability in the WordPress RokBox WordPress plugin, affecting versions <= 2.13. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2012, reported by Eugene Dokukin.
Vulnerability Overview
The WordPress RokBox plugin is vulnerable to Denial of Service via the 'src' parameter in the 'thumb.php' file in versions up to, and including, 2.13. This makes it possible for unauthenticated attackers to slow the response time of the vulnerable service to an unusable speed and/or completely deny it.
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 availability.
CWE-400: Uncontrolled Resource Consumption
WordPress RokBox <= 2.13 carries this weakness at src, and reaching it takes a caller who can reach the endpoint. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. No fixed build of this plugin is recorded for WordPress RokBox yet, so installs running <= 2.13 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to WordPress RokBox: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WordPress RokBox
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C