HexBrain

U.S. Dept Of Defense · Report #235041

Sensitive Email disclosure Due to Insecure Reactivate Account field

Validstatus
mediumseverity
3upvotes
2 Dec 2019disclosed

Summary

An insecure activation field allowed attackers to harvest emails of users if the attacker knew the user name of a user. This allowed me to leak the email of an administrative account and this could lead to further targeted attacks by attackers.

How it was found

Summary: An attacker could discover the emails of accounts on ██████ through the reset field. Description: https://████/███/accounts/request_reactivation/ This password reset field has no rate limiting, it additionally allows an attacker to guess at user accounts such as admin and it will then expose the account user's email. For example, I used admin for my example and was given this email,████████. Normally password reset fields keep the account emails hidden to prevent any attempt to directly attack the user, for example phishing emails.

Impact

Medium

Step-by-step Reproduction Instructions

  1. Visit https://███/██████████/accounts/request_reactivation/
  2. Enter admin and then submit
  3. You will receive the following text

Activation Email Sent

We've sent an email to██████ containing a link that will reactivate your account.

If███████ is not your email address, please contact the GRiD team and we will be happy to assist you.

Suggested Mitigation/Remediation Actions

I would recommend changing the account reset field to log any attempts for password resets to check for any malicious or abusive attempts to harvest account names, set a limit for amount of requests for the field, and additionally make a general message such as "We have sent the reset request to the email you used on registration"

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original