Vulnerability reports consist of different components that are good to understand when viewing them on Hacktivity or in your inbox.
The hacker that submitted the report is shown in the sidebar metadata. On hover, you can see the hacking statistics by reputation, signal, and impact.
Report ID and Title
At the top of the report is the report ID number and title. You can change the report title to your internal naming conventions. The color behind the report number represents the state the report is in. These are the different colors and the report states they represent:
Needs more info
Pending Program Review (currently in beta)
You’ll be able to view these metadata fields in the right sidebar:
The specific asset the vulnerability was found on.
(An internal field that is only seen by the program’s security team) The person on your security team that's assigned to triage or manage the report.
(Only shows for resolved reports that were given a bounty) How much bounty the report was awarded.
Shows which report this was cloned from
There is an ability to clone a report on our platform, this metadata item links all the reports that were cloned from the current one.
Credential Account Details
Related to Credential Management (https://docs.hackerone.com/organizations/credential-management.html)
Private fields for your company, not seen by hackers see the article about custom fields
The CVE ID the vulnerability is linked to.
The date the report was disclosed. Only shows for reports that were disclosed.
Shows which reports this is a duplicate of
Ability to generate a secure link to share this report with a third party
Indicates whether you have notifications enabled or disabled for actions on your program.
All of the hackers involved in finding the vulnerability as well as program members involved with triaging the report.
(Shows only if you're participating in pentests) The pentest the report is linked to.
(An internal field that is only seen by the program’s security team) The ticket number associated with the report in your issue tracking tool that you've set up an integration for.
The date and time the report was submitted.
The name of the program the report was submitted to.
The hacker who submitted the report
Programs have certain SLA, so this is date/time by which the program should resolve the report, so it doesn't miss SLA
The severity level of the vulnerability.
The state the report is in.
Indicates the status of disclosure of the vulnerability. You can also choose to redact private information from the report.
The type of weakness of the vulnerability.
Either your security team or the hacker(s) involved with the report can choose to provide an optional summary of the report. Including a summary helps future viewers of the report to understand the context without having to scroll through the entire report. Click ADD SUMMARY to add a summary to the report.
The report timeline shows all of the activity that occurs in the report between the hackers and the program members involved with triaging the report. It will show when:
A hacker or a program member adds a comment
The state of the report changes
A bounty is set
A bounty has been given
A hacker requests mediation
A hacker or program member requests public disclosure
An internal activity has been made
The severity level has changed
The report timeline will also show who is in charge of the next pending action within the report.