Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 973386 - wordpress: denial of service in password-protected posts
wordpress: denial of service in password-protected posts
Status: CLOSED DUPLICATE of bug 973254
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 973256 973257 973390 973391
  Show dependency treegraph
Reported: 2013-06-11 16:18 EDT by Vincent Danen
Modified: 2013-06-12 05:06 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-12 05:04:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vincent Danen 2013-06-11 16:18:43 EDT
A denial of service vulnerability was reported in WordPress 3.5.1 [1],[2] that could allow a remote unauthenticated user to exhaust CPU and memory resources by sending an HTTP request with a specially-crafted password cookie to a WordPress URL of a password-protected post.  This vulnerability is caused by an error when calculating the hash cycle count within the crypt_private() method in wp-includes/class-phpass.php.There is currently no upstream fix for this, and it requires the attacker to have knowledge of a WordPress site's password-protected post URL, if there is one.

[1] http://seclists.org/oss-sec/2013/q2/541
[2] https://vndh.net/note:wordpress-351-denial-service
Comment 1 Vincent Danen 2013-06-11 16:30:57 EDT
Created wordpress tracking bugs for this issue

Affects: fedora-all [bug 973390]
Affects: epel-all [bug 973391]
Comment 2 Jan Lieskovsky 2013-06-12 05:04:44 EDT

*** This bug has been marked as a duplicate of bug 973254 ***

Note You need to log in before you can comment on or make changes to this bug.