HexBrain

HackerOne · Report #1128701

Lack warning label when receiving a letter

Validstatus
lowseverity
33upvotes
13 May 2021disclosed

How it was found

Summary:

Hi team,

When using the function ShareReportViaEmail the email is sent to the email address specified by the hacker.This email looks legitimate and comes from verification email addresses, leaving no doubt about it being replaced. This endpoint also applies to sandbox reports which makes it possible to insert any information.

Our team believes that it is worth adding a label that would warn that this email was sent from a sandbox report, which would make it clear about possible social engineering, for example, how is it done when you are invited to a sandbox program

Steps To Reproduce:

  1. Create sandboxed program
  2. Create fake asset, for example : https://hackerone.com
  3. Create report

Asset: https://hackerone.com , Weakness: SQL Injection (cwe-89), Severity: Critical

  1. GraphQL query:

{"query":"mutation Createvpncredentialsmutation($input0:ShareReportViaEmailInput!) {shareReportViaEmail(input:$input0) {errors{edges{node{field,message,type}}},was_successful,clientMutationId}}","variables":{"input0":{"message":"If you would like to participate in the retest of this report , the payout for retest is 500$, please reply to this email : [[email protected]] and we will send you an invite [HackerOne Retest Team]","emails":"[email protected]","report_id":"gid://hackerone/Report/ID_SANDBOXED_REPORT","clientMutationId":"0"}}}

{F1233403}

In our opinion, this letter looks very plausible, which may provoke a response to send a response from the original mail to @wearehackerone.com, thereby revealing he email. Because to pay the retest, you will need the original account

Recommendation:

Our team believes that it makes sense to add a warning to this email template, indicating that it was sent from the sandbox and may not be related to the data specified in it

Thanks!

Impact

The ability to get hackers ' email through social engineering

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