Skip to main content

Duplicate Reports

Organizations: What happens when a hacker reports a vulnerability that has already been reported

Updated over a week ago

When a hacker reports a vulnerability that has already been reported, it's considered a duplicate report. When you mark a report as a duplicate, you can choose between these two options:

Option

Details

1

Add the second hacker as an external participant on the original report.
​
This means the second hacker will be able to view the contents of the original report. They can see all comments and activity on the report that the original hacker sees and comment on the report as well. This applies to any subsequent hackers (3rd, 4th, etc.) who submit the same duplicate report and are added to the original report.

2

Don't add the hacker as an external participant on the original report.
​
Instead, you can inform the hacker that their submitted vulnerability is a duplicate and list the original report number in the comments section.

Adding a Hacker to the Original Report

To add the hacker to the original report:

  1. Go to the bottom of the report above the comment box.

  2. Change the action picker to Close report > Duplicate.

  3. Enter the original report number in the Search report field and select the report from the selection list.

  4. A checkbox stating Add hacker name to the original report will show under the Search report field.

  5. Select the checkbox to add the hacker to the report.

Marking a report as duplicate in the inbox

Your program decides whether to share the original report with the hacker who submitted the duplicate. We recommend linking the duplicate to the original to ensure accountability and to apply reputation changes to the right hacker.

Did this answer your question?