Retesting

As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of data. Programs can elect to invite you and other hackers to retest your vulnerabilities to verify fixes.

There’s currently no effect to reputation for participating in the retest. Although there’s no time limit, we recommend you to complete the retest within 24 hours after accepting the invitation.

If you’re invited to retest a vulnerability, you’ll receive an invitation in your email to retest the report.

retesting-1

If you're the original reporter of the report, you'll also receive an email asking you to participate in retesting your report.

retesting email for original reporter

To participate in the retest:

  1. Click View retest invitation in your email.
  2. Accept or Reject your invitation for retesting. Note: The invitation is only valid for 24 hours.

retesting invitation

  1. Familiarize yourself with the contents of the report and check to see that the vulnerability has been fixed.
  2. Click the answer these questions link in the report banner or just scroll to the bottom of the report to access the questionnaire.

retesting-2

  1. Answer these questions in the questionnaire:

    • Are you able to reproduce the vulnerability?
    • Are you able to identify a bypass to the fix?

retesting questionnaire

  1. Submit a new report if you found a new vulnerability by clicking on the submit a new report link, and enter the report ID number in the Report ID field.

retesting-4

  1. Provide a short summary of how you retested the vulnerability and upload any attachments of your validations.

retesting summary and attachments example

  1. Click Submit.
  2. Click Yes! to finalize your submission.

retesting-5

Upon completion, you'll be awarded with a $50 bounty.