Bug 973386 - wordpress: denial of service in password-protected posts
Summary: wordpress: denial of service in password-protected posts
Status: CLOSED DUPLICATE of bug 973254
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
(Show other bugs)
Version: unspecified
Hardware: All Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=low,public=20130607,reported=2...
Keywords: Security
Depends On: 973256 973257 973390 973391
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-11 20:18 UTC by Vincent Danen
Modified: 2013-06-12 09:06 UTC (History)
4 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vincent Danen 2013-06-11 20:18:43 UTC 
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 20:30:57 UTC 
Created wordpress tracking bugs for this issue

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

*** 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.