Bug 1449197 (CVE-2017-8295) - CVE-2017-8295 wordpress: Usage of Host HTTP header for a password-reset e-mail message
Summary: CVE-2017-8295 wordpress: Usage of Host HTTP header for a password-reset e-mai...
Alias: CVE-2017-8295
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1449199 1449198
TreeView+ depends on / blocked
Reported: 2017-05-09 12:06 UTC by Andrej Nemec
Modified: 2019-09-29 14:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-08 03:12:08 UTC

Attachments (Terms of Use)

Description Andrej Nemec 2017-05-09 12:06:31 UTC
WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to transmission of the reset key to a mailbox on an attacker-controlled SMTP server. This is related to problematic use of the SERVER_NAME variable in wp-includes/pluggable.php in conjunction with the PHP mail function. Exploitation is not achievable in all cases because it requires at least one of the following: (1) the attacker can prevent the victim from receiving any e-mail messages for an extended period of time (such as 5 days), (2) the victim's e-mail system sends an autoresponse containing the original message, or (3) the victim manually composes a reply containing the original message.



Comment 1 Andrej Nemec 2017-05-09 12:06:48 UTC
Created wordpress tracking bugs for this issue:

Affects: epel-all [bug 1449199]
Affects: fedora-all [bug 1449198]

Comment 2 Product Security DevOps Team 2019-06-08 03:12:08 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.

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