Cdkeysdeals Bug Bounty Program
Although our team of experts has made every effort to mitigate all the bugs in our systems, Cdkeysdeals invites independent security groups and individual researchers to study it across all platforms and help us make it even safer for our customers. If you discover a bug, we appreciate your cooperation in responsibly investigating and reporting it to us so that we can address it as soon as possible. For Security-related bugs/vulnerabilities, we offer reward and recognition (below).
Though we welcome reporting of non-security issues at https://www.cdkeyseals..com/support, please note that only genuine security issues are eligible for rewards.
In case of any issues related to fraud, please report them to firstname.lastname@example.org
Participating in bug bounty program requires you to follow our guidelines. Responsible investigation and reporting include, but not limited to the following:
Don't violate the privacy of other users, destroy data, disrupt our services, etc.
Only target your own accounts in the process of investigating any bugs/findings. Don't target, attempt to access, or otherwise disrupt the accounts of other users.
Don't target our physical security measures, or attempt to use social engineering, spam, distributed denial of service (DDOS) attacks, etc.
In case you find a severe vulnerability that allows system access, you must not proceed further.
It is Cdkeysdeals decision to determine when and how bugs should be addressed and fixed.
Disclosing bugs to a party other than Cdkeysdeals is forbidden, all bug reports are to remain at the reporter and Cdkeysdeals discretion.
The threatening of any kind will automatically disqualify you from participating in the program.
Exploiting or misusing the vulnerability for own or others benefit will automatically disqualify the report.
In general, please investigate and report bugs in a way that makes a reasonable, good faith effort not to be disruptive or harmful to us or our users. Otherwise, your actions might be interpreted as an attack rather than an effort to be helpful.
Generally speaking, any bug that poses a significant vulnerability could be eligible for a reward. But it's entirely at our discretion to decide whether a bug is significant enough to be eligible for a reward.
Security issues that typically would be eligible (though not necessarily in all cases) include:
Cross-Site Request Forgery (CSRF)
Cross-Site Scripting (XSS)
Server-Side Request Forgery (SSRF)
File inclusions (Local & Remote)
Protection Mechanism bypasses (CSRF bypass, etc.)
Leakage of sensitive data
Administration portals without an authentication mechanism
Open redirects which allow stealing tokens/secrets
Things that are not eligible for reward include:
Application stack traces (Path disclosures, etc.)
Self-type Cross-Site Scripting
Denial of Service attacks
CSRF issues on actions with minimal impact
Brute force attacks
Security practices (banner revealing a software version, etc.)
Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website.
Vulnerabilities contingent on physical attack, social engineering, spamming, DDOS attack, etc.
Vulnerabilities affecting outdated or unpatched browsers / Operating Systems.
Vulnerabilities in third-party applications that make use of Kraken's API.
Bugs that have not been responsibly investigated and reported.
Bugs already are known to us, or already reported by someone else (reward goes to the first reporter).
Issues that aren't reproducible.
Issues that we can't reasonably be expected to do anything about.
Reports of current or previous employees of Cdkeysdeals and subsidies and partners
All monetary rewards can ONLY be credited to a Cdkeysdeals wallet, subject to verification.
The minimum reward for eligible bugs is the equivalent of 1000 INR / 20 EURO.
Only one reward per bug.
Rewards over the minimum are at our discretion, but we will pay significantly more for particularly serious issues. We will also issue Certificate of recognition to distinguished individuals.
Multiple reports over time can be eligible for Hall of Fame.
Depending on the report, reports may be eligible for a digital certificate rather than a bounty.
How to Report a Bug?
Fill the form (Findings reported by other ways will not be acknowledged).
Include as much information in your report as you can. Ideally, a description of your findings, the steps needed to reproduce it, and the vulnerable component.
If you need to share screenshots/videos for PoC, please upload to your own Google Drive or any other upload service and share with us the links to those files in the form.
Include your correct name and email address so we can reach out to you.
Allow us up to 7 days to respond before sending another email on the matter.