DSPH Security Bug Bounty Program

Introduction

Software security researchers are increasingly engaging with Internet companies to hunt down vulnerabilities. Our bounty program gives a tip of the hat to these researchers and provides rewards as HOF and appreciation letter or more for critical vulnerabilities. Below you can find information about the rules, scope and reporting requirements.Happy hacking!

Please Do follow

  • We accept bug only throught our  support ticket system
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data
  • Do not reveal the problem to others until it has been resolved
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties
  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation

What we promise

  • If you have followed the instructions above, we will not take any legal action against you in regard to the report
  • We will not share your personal details with third parties without your authorisation, unless required in order to do so to comply with legal obligations
  • We will make reasonable efforts to respond quickly, to confirm receipt of the vulnerability report and to provide a summary of our initial findings.

Scope

  • dsph.org
  • *.dsph.org
  • darksocietypenetration.com
  • *.darksocietypenetration.com

Out of scope

Some findings do not need to be disclosed as they have low security impact. This section contains a listing of issues found to be commonly reproducible and reported. Vulnerabilities included within the following categories do not need to be notified:

  • 404 HTTP page errors
  • Banner disclosures
  • SSL/TLS insecure ciphers
  • Missing HTTP security headers
  • TRACE/OPTIONS HTTP methods enabled
  • Logout CSRF
  • Clickjacking attacks
  • Public files or directories disclosure (readme.html, robots.txt, sitemap.xml)
  • Secure and HTTPOnly cookie flags

We strive to remediate all identified vulnerabilities as quickly as possible, and where applicable, we would like to play an active role in the ultimate publication on the vulnerability after it has been remediated.

How to report

  1. Visit our  support ticket system
  2. Make a ticket with   TYPE -> Bug Report
  3. In the subject field name the vulnerability
  4. In message box provide a short description of the bug
  5. Attacked a POC in PDF and submit the report