BUG BOUNTY

OverviewHow it worksThe Syfe PromiseRewardsHall of Fameoverviewoverviewoverview
overviewoverviewoverview

Syfe security custodian

Keeping user information safe and secure is a top priority for us at Syfe, and we welcome the contribution of external security researchers.

Introducing Bug Bounty

Syfe welcomes feedback from security researchers and the public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.

How it works

How to submit a Report

Please submit all vulnerability reports and claim test credentials directly via our official HackerOne bug bounty platform: https://hackerone.com/syfe_bbp/

Systems in Scope

For the most updated list of in-scope and out-of-scope assets, please consult our HackerOne programme page.

The Syfe promise

Our Commitments
Our expectations
Safe harbour

When working with us, according to this policy, you can expect us to

  • Respond to your report promptly, and work with you to understand and validate your report;
  • Strive to keep you informed about the progress of a vulnerability as it is processed;
  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
  • Extend Safe Harbor for your vulnerability research that is related to this policy.

Provided you abide with the following when conducting vulnerability research under this policy, we consider this research conducted under this policy to be entitled to the safe harbour protections mentioned here under:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
  • Report any vulnerability you’ve discovered promptly;
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
  • Use only the Official Channels to discuss vulnerability information with us;
  • Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
  • You should only interact with test accounts you own or with explicit permission from the account holder; and
  • Do not engage in extortion.

Our programme offers Safe Harbor and follows gold-standard disclosure policies. Please review the full terms on our HackerOne programme page.

In recognition of your service

Rewards

Syfe will provide a reward for qualifying vulnerabilities that are discovered by you. A “qualifying vulnerability” is one that is determined by Syfe, at its sole and absolute discretion:

  • to meet the requirements of this policy;
  • as not being excluded under this policy; and
  • and has not been previously discovered or disclosed to Syfe by any other person.

Participation in our vulnerability disclosure programme does not constitute a contract between Syfe and you. Syfe will determine any eligibility for a reward under this programme at its sole and absolute discretion. You are not entitled to, and Syfe is not obliged to and does not undertake to provide, any legal or equitable remedy for any participation in this programme.

Reward details and eligibility criteria are managed directly on our HackerOne programme page.

Hall of Fame

Syfe Security would like to thank the following Security Researchers for their contributions in making Syfe more secure by responsibly disclosing security issues to us via Syfe Bug Bounty.

Note: From March 2025, the Syfe Bug Bounty Programme has moved to HackerOne. This page will no longer be updated, but will remain here to show our gratitude to those who have contributed to our programme. You can find our new Hall of Fame (https://hackerone.com/syfe_bbp/thanks) on our HackerOne programme page (https://hackerone.com/syfe_bbp/).

2024
SUVENDU DASH
Sankalpa Baral
Zain Iqbal
Gaurang Maheta
Bhavya Trivedi
Dishant Chavda
Vaibhav Shinde
Roneil Bordallo
Rohan Agarwal
2023
Soumyaranjan Das
2022
Sohail Ahmed

ISSUES

Excluded from scope

close
Description
Reason
Network-level Denial of Service (DoS/DDoS) vulnerabilities.
We do not want you to disrupt any of our services.
Low severity issues that can be detected with tools such as Hardenize and Security Headers.
We run regular scans with these services and try to improve our score gradually.
Content injection issues.
The severity of this issue is so low that it does not warrant a report.
Cross-site Request Forgery (CSRF) with minimal security implications (Logout CSRF, etc.).
In order for CSRF to be a valid issue it must affect some important action such as deleting one's account.
Missing cookie flags on non-security-sensitive cookies.
These types of issues do not present a major risk and are usually picked up by scanners.
UI and UX bugs (including spelling mistakes).
No comment.
401 injection.
This is usually an accepted risk and we are already aware of this issue.
Stack traces that disclose information.
All of our projects are open-source therefore this information is usually public knowledge. That said, if you discover a stack trace that discloses information which is not located in our GitHub repositories, please do submit a report.
Host header issues without an accompanying proof-of-concept demonstrating vulnerability.
We require a clear proof of concept.
Open ports without an accompanying proof-of-concept demonstrating vulnerability.
Same as above.
Banner grabbing issues (figuring out what web server we use, etc.).
We will happily share what web servers we are running.
Missing X-Frame-Options header (Clickjacking)
The lack of X-Frame-Options does not always indicate that a security vulnerability is present. This is an optional header that is only necessary on endpoints where there UI is rendered to invoke state changing actions. We recommend reading this RFC by David Ross: 
https://datatracker.ietf.org/doc/rfc7034/
Cross-site tracing
In order for Cross-Site Tracing (XST) to really be a significant issue you would need to find an endpoint vulnerable to Cross-site Scripting (XSS).
CSP uses unsafe-inline
The fact that a CSP includes unsafe-inline is not an issue in itself. In order for you to demonstrate the actual impact of this value, we highly recommend you look for an XSS vulnerability. Try to trigger alert(document.domain).
Disclosure of robots.txt file
We are aware that in some cases robots.txt files have been known to disclose sensitive information. In our case we have determined that our robots.txt files do not contain any information that poses a potential security risk.
Email spoofing 
(SPF misconfigurations)
We have accepted the risk that this issue poses and do not believe that it warrants an immediate fix.
Open redirect using 
Host header
Open redirects in the Host header are not exploitable.
User enumeration
See https://security.stackexchange.com/a/200612/192205.