Bug Report
A Report that is submitted on BugBase has comprehensive information about a vulnerability. Below are a few pointers that may help you to understand on how to analyse a report on BugBase
A Bug Report has the following information in it:
Report Title
Vulnerability Category
Affected Asset
Affected URL (Optional)
Severity Score (CVSS)
Priority (Based on Severity Score)
Vulnerability Impact
Proof Of Concept (POC) of the Vulnerability
Brief Summary of the Vulnerability
Attachments along with the POC (Optional)
Status of the Report
Reporter Details (Username of the Reporter)
The company representative can converse with the reporter about the details of the vulnerability and discuss impact and remediations.
A Chat Functionality is provided in the Report View for a quick doubt resolution with the report in case more context is required on the POC.
Bug Reports can also be shifted to a different program in the same organization - companies usually do this to segregate reports by scope or confidentiality.
Reporters are provided with an alias email by BugBase, in the format [username]@teambugbase.com, on which the reporter can receive emails. If any sensitive information is to be shared with the reporter, you can use the alias email to contact them.
Next, know more about the Report Lifecycle and Status
Last updated