SMTP2GO is a fast and scalable email service provider, for sending transactional and marketing emails and viewing reports on email delivery.
SMTP2GO has previously run a Vulnerability Disclosure Program (VDP) and made the switch to a Bug Bounty Program in order to further enhance our product security. We look forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.
SMTP2GO will make a best effort to meet the following SLAs for hackers participating in our program:
| Type of Response | SLA in business days |
| ------------- | ------------- |
| First Response | 2 days |
| Time to Triage | 2 days |
| Time to Bounty | 5 days |
| Time to Resolution | depends on severity and complexity |
We’ll try to keep you informed about our progress throughout the process.
Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Follow HackerOne's disclosure guidelines.
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Free trial: You may register up to two test accounts on the SMTP2GO website (https://www.smtp2go.com/pricing/). However, please make sure to use your Hacker Email Alias - [username]
@wearehackerone.com and [username+test]
@wearehackerone.com when creating accounts for our tracking purposes.
Paid accounts: There are additional permissions that are not accessible to free accounts like Email Archiving, Email Testing and the addition of Dedicated IP Addresses.
For those who wish to conduct testing with our paid Professional accounts, we will be providing access upon request.
To request the paid account access, please email email@example.com with the subject title “H1 - SMTP2GO Paid account request”. In the email, please provide the following information:
Your HackerOne username
The email you have used to register on SMTP2GO (this should be your Hacker Email Alias as instructed previously)
Requests will be approved in two working days and you will be informed once the access is provided.
Clickjacking on pages with no sensitive actions
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Attacks requiring MITM or physical access to a user's device.
Previously known vulnerable libraries without a working Proof of Concept.
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Missing best practices in SSL/TLS configuration.
Any activity that could lead to the disruption of our service (DoS).
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Rate limiting or bruteforce issues on non-authentication endpoints
Missing best practices in Content Security Policy.
Missing HttpOnly or Secure flags on cookies
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
Open redirect - unless an additional security impact can be demonstrated
Issues that require unlikely user interaction
User enumeration, unless you can demonstrate that a brute force attack is likely to succeed.
The ability to send an email from any domain name (not just one of your account's verified Sender Domains). This is only considered a vulnerability if the email becomes DKIM-signed with a DKIM signature at that same domain name, or the email passes DMARC. For example, you manage to send an email from
firstname.lastname@example.org and it becomes signed with a DKIM signature with d=anotherdomain.com.
Issues with notification emails, as the notification system is currently being overhauled.
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep SMTP2GO and our users safe!
|Scope Type||Scope Name|
|Scope Type||Scope Name|
This policy crawled by Onyphe on the 2020-07-21 is sorted as bounty.