Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
555,864 coordinated disclosures
356,678 fixed vulnerabilities
845 bug bounties with 1,632 websites
17,373 researchers, 1153 honor badges

Snovio Inc Bug Bounty Program

Snovio Inc runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of Snovio Inc

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between Snovio Inc and researchers.

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

snov.io

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

Snovio believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security bug in the services listed in our scope, we will be happy to work with you to resolve the issue promptly and ensure you are fairly rewarded for your discovery.

Scope

At this time, the scope of this program is limited ONLY to security vulnerabilities found on domain https://app.snov.io

Vulnerabilities reported on other properties (including https://snov.io) or applications are currently NOT eligible for monetary reward. High impact vulnerabilities outside of this scope might be considered on a case by case basis.

In-Scope Sub-Domains:
https://app.snov.io

Out-of-Scope Domains and subdomains:
https://snov.io
https://*.snov.io

Testing Requirements:

You can create a free account at https://app.snov.io/login and register for testing purposes.

* Any vulnerability found must be reported no later than 24 hours after discovery.
* You are not allowed to disclose details about the vulnerability anywhere else.
* You must avoid tests that could cause degradation or interruption of our service.
* You must not leak, manipulate, or destroy any user data.
* You are only allowed to test against accounts you own yourself.
* The use of automated tools or scripted testing is not allowed.

Possible Awards:

The standard reward is $50.

To qualify for a reward under this program, you should:

* Be the first to report a vulnerability.
* Include attachments such as screenshots or proof of concept code as necessary.
* Send a clear textual description of the report along with steps to reproduce the vulnerability.
* Disclose the vulnerability report directly and exclusively to us.

A good bug report should include the following information at a minimum:

* List the URL and any affected parameters
* Describe the browser
* Describe the perceived impact.
How could the bug potentially be exploited?
Any video or screenshot can be helpful.

Special Notes:

Our bug bounty program is limited strictly to technical security vulnerabilities of Snovio services listed in the scope. Any activity that would disrupt, damage or adversely affect any third-party data or account is not allowed.

Please do not mass create accounts to perform testing against Snovio applications and services. Also, do not perform brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality.

The following are strictly prohibited:

* Denial of Service attacks.
* Physical attacks against offices and data centers.
* Social engineering of our service desk, employees or contractors.
* Compromise of Snovio users or employees account.
* Automated tools or scans, botnet, compromised site, end-clients or any other means of large automated exploitation or use of a tool that generates a significant volume of traffic.

Additionally, the following vulnerabilities will not be considered for bounty:

* Cross-site request forgery (CSRF)
* Cross domain leakage
* Information disclosure
* Software version disclosure
* XSS attacks via POST or headers
* Self-xss
* Missing SPF or DMARC records
* HttpOnly and Secure cookie flags
* SSL/TLS related (such as HSTS, GET over HTTP, Password sent in HTTP)
* Session timeout
* Session Hijacking (cookie reuse)
* Missing X-Frame or X-Content headers
* Account enumeration
* Click-jacking
* Rate-limiting
* Confirmation Email (anything related with)

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  How quickly researchers get responses to their submissions.
Remediation Time  How quickly reported submissions are fixed.
Cooperation and Respect  How fairly and respectfully researchers are being treated.

Researcher's comments

No comments so far.

  Latest Patched

 12.08.2020 prisguiden.no
 12.08.2020 daveramsey.com
 12.08.2020 2gis.kz
 12.08.2020 themoviedb.org
 12.08.2020 arb.ca.gov
 12.08.2020 lightningmaps.org
 12.08.2020 univ-poitiers.fr
 12.08.2020 wirtualnemedia.pl
 11.08.2020 wuzzuf.net
 11.08.2020 inmotionhosting.com

  Latest Blog Posts

24.06.2020 by Gkexamquiz
How to Find Contacts To Report Bugs & Security Vulnerabilities | Bug Bounty Tutorials 2020
24.06.2020 by 0xcrypto
Improper Access Control - Generic: Unrestricted access to any "connected pack" on docs in coda.io
04.04.2020 by Rando02355205
(Alibaba) message.alibaba.com [IDOR] - [Bug Bounty]
12.03.2020 by Rando02355205
(Paypal) www.paypal.com [CSP High Level] - [XSS Reflected] - [Bug Bounty] - [Write Up]
08.03.2020 by CybeReports
JDECO.net XSS Vulnerability| CybeReports

  Recent Recommendations

    12 August, 2020
     www_aasv_org:
Caught me having forgotten to entity-encode values when re-displaying an incomplete form submission. While the initial report was all I needed to patch, Rajash considerately provided additional detail without being asked through the openbugbounty comments.
    10 August, 2020
     msawired:
Thank you for reporting the XSS vulnerability. Your explanations were very helpful, and we were able to resolve the issue in no time.
    6 August, 2020
     Robert_CMI:
Thank you Rajesh for reporting vulnerabilities on our website, your quick and detailed response was very valuable to us!
    6 August, 2020
     StefanCink:
Thanks to @singhnitesh21 we were able to close a vulnerability on our website asap. Thank you!
    5 August, 2020
     kkb5mobile:
Thank you for pointing out the vulnerability.
Thanks to you, I was able to respond safely.