SendPulse Bug Bounty Program

Bug Bounty Scope

The following websites are within the scope of the program:

Non-Intrusive Submissions Handling

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

General Requirements:

No technology is perfect, and SendPulse 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://login.sendpulse.com

Vulnerabilities reported on other properties (including https://sendpulse.com) 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://login.sendpulse.com

Out-of-Scope Domains and subdomains:
https://sendpulse.com
https://*.sendpulse.com

SendPulse mobile application for iOS and Android is also not in-scope for this program.

You will qualify for a reward only if you are the first person to responsibly disclose an unknown issue. The SendPulse security team has 30 days to respond to the report, and up to 90 days to implement a fix based on the severity of the report.

Please allow for this process to fully complete before attempting to contact us again. Note that posting details or conversations about the report or posting details that reflect negatively on the program and the SendPulse brand, will result in immediate removal from the program.

Testing Requirements:

You can create a free account at https://sendpulse.com/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.
* Send a clear textual description of the report along with steps to reproduce the vulnerability.
* Include attachments such as screenshots or proof of concept code as necessary.
* 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 and OS
* Describe the perceived impact. How could the bug potentially be exploited?
Videos and/or screenshots can be helpful.

Special Notes:

Our bug bounty program is limited strictly to technical security vulnerabilities of SendPulse 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 SendPulse 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 SendPulse 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)