Getatlas E909rh35zb

HackerOne

Stay updated on the status of all your company's support tickets.

Customer portal

After you submit a vulnerability report on HackerOne, it enters a process of review, validation, and resolution. Understanding the different stages and reporting statuses associated with this process will help you navigate the journey of your report, track its progress, and understand the actions taken by the program team. 

  The program team first reviews your report and its associated PoC to confirm that it's a legitimate vulnerability. This stage focuses on verifying the accuracy of the information provided and ensuring the issue meets the program's criteria. 

  The program team analyzes the severity and potential impact of the vulnerability. This involves considering factors like the exploitability, the scope of impact, and the potential for harm. Vulnerabilities are then prioritized based on their severity and potential impact.  

  During the triage process, the program team will communicate with you, providing updates on the status of your report. This may involve requesting additional information, clarifying details, or providing feedback on your findings. 

 Once a vulnerability is validated, the program team works with the responsible parties to develop and implement a fix or remediation plan. This may involve patching software, updating configurations, or implementing security controls.

  Upon successful resolution, the program team may publicly disclose the issue, crediting you for your discovery. This can include publishing a security advisory, providing a bug bounty reward, or offering other forms of recognition.

  Your report has been submitted and is awaiting initial review by the program team.

 The program team has reviewed your report, validated the vulnerability, assigned a severity level, and determined the next steps.

  The program team is actively working with the responsible parties to develop and implement a fix or remediation plan.

  The vulnerability has been addressed, and the program team has confirmed the fix is in place.

 The vulnerability has been re-opened due to a failed fix, new information, or a recurrence of the issue.

A guide to the different reporting statuses and what they mean for your submitted vulnerabilities.

Understanding Vulnerability Triage and Reporting Status

HackerOne provides a comprehensive support system to assist you with any questions, concerns, or issues you might encounter while using the platform. Whether you need help with reporting vulnerabilities, understanding program guidelines, or resolving technical issues, HackerOne support is there to provide guidance and assistance. 

  Access the HackerOne Help Center (https://support.hackerone.com/) for a wealth of documentation, articles, and frequently asked questions (FAQs). Find answers to common questions and explore resources that provide guidance on various aspects of the platform.

  Visit the HackerOne Support page (https://support.hackerone.com/hc/en-us/requests/new) to submit a support ticket.  Provide a clear description of your issue, your account details, and any relevant screenshots or information that helps explain your problem.

 If you prefer, you can email the HackerOne support team at support@hackerone.com.

  When submitting a support ticket, provide as much detail as possible about your issue. Include specific steps you've taken, error messages, or relevant screenshots. 

 Clearly state your problem and what you're trying to achieve.  Avoid using vague language or making assumptions. 

 Before submitting a support ticket, search the HackerOne Help Center for existing articles or FAQs that might address your issue. 

 HackerOne support strives to respond to inquiries as promptly as possible, but it may take some time for them to investigate and resolve your issue.

Information on how to contact HackerOne support and get help with specific issues or questions.

Contacting HackerOne Support

Submitting vulnerability reports on HackerOne is a crucial part of the ethical hacking process, but sometimes you may encounter issues that prevent you from successfully submitting your report.  This guide addresses common reporting problems and provides solutions to help you overcome these obstacles. 

 Double-check that you've selected the correct vulnerability type from the dropdown menu. Choose the category that most accurately describes the vulnerability you've discovered.

 Ensure your PoC provides clear and convincing evidence of the vulnerability.  Include detailed steps to reproduce the issue, screenshots, videos, or technical explanations to support your report.

 Provide clear and detailed steps on how to reproduce the vulnerability.  The program team needs to be able to easily replicate the issue to verify its existence and impact. 

  Write a detailed and well-written description of the vulnerability, including the impact it could have and any relevant technical information.  Avoid using jargon or overly technical language that might be difficult to understand.

  Avoid including sensitive data or confidential information in your report.  Focus on providing the necessary technical details to demonstrate the vulnerability without disclosing unnecessary information. 

  Thoroughly review the program's specific guidelines before submitting your report.  Program guidelines outline acceptable reporting methods, reporting requirements, and specific details about the program's scope. 

  Check existing reports to ensure you're not reporting a duplicate issue that's already been addressed. 

  Make sure your report falls within the scope of the program.  Refer to the program's scope description to confirm that the reported issue is relevant to the program's objectives.

Troubleshooting tips for addressing common errors and issues you might encounter while submitting reports.