Here at BrickFTP, we celebrate security and we encourage independent security
researchers to help us keep our products secure.
We offer a Security Bug Bounty Program (the "Program") to create an incentive
and reward structure so that researchers are able to devote resources to
working on BrickFTP.
We will pay $100 to $10,000, at our discretion, to any researcher who
discovers a significant security vulnerability in BrickFTP. We pay quickly and
fairly, every time, as long as you follow our rules.
If you've found a vulnerability or would like to perform security research
against BrickFTP, please read through the rules below.
Reports We Are Looking For
We want to know about anything about our platform that poses a significant
security vulnerability to either us or our customers.
These can include:
- Privilege Escalation
- Authentication Bypass
- Leakage of Sensitive Data
- Remote Code Execution
- SQL Injection
- Cross-Site Request Forgery (XSRF)
- Cross-Site Scripting (XSS)
- Code Injection
- ... and more!
Bug Bounty Program Requirements
To participate in our program, you must create trial account on our platform
by navigating to BrickFTP.com and clicking the button to start a Free Trial.
VERY IMPORTANT : Your account must include the phrase "[ BUGBOUNTY ]"
in the "Company Name" used when registering. (Without quotes, but with square
Absolutely do not under any circumstances input payment card information
(credit card or debit card) or make a payment unless you intend to pay the
charge in full. If you properly tag your account as a bug bounty site by
following the directions above, we will not prompt you for payment during your
Failure to abide by the above will result in your full disqualification from
- Do not create more than one trial account within a 60-day period for the purpose of conducting security research against our platform.
- Do not attempt to gain access to another user's account or data.
- Do not impact other users with your testing.
- Do not perform any attack that could harm the reliability/integrity of our services or data. DDoS/spam attacks are not allowed.
- Do not publicly disclose a bug either before or after it has been fixed. Public disclosure means disclosure to anyone, even on private "Hacker" websites and forums.
- Do not attempt non-technical attacks such as social engineering, phishing, or physical attacks against our employees, users, or infrastructure.
- Do not upload information about the vulnerability to any site you do not directly own. This includes uploading videos to YouTube, Vimeo, etc, even if marked private.
- Any scanners or automated tools used to find vulnerabilities need to be rate limited.
- Decisions made by us regarding the eligibility of submissions are final. Do not write back to dispute a decision.
- You are expected to be 100% professional and pleasant to work with via E-Mail.
Reports That Do Not Qualify
The following types of reports do not qualify and will not pay a bounty.
- Vulnerabilities on the BrickFTP.com marketing website or support website, unless they lead to a vulnerability on the actual BrickFTP platform.
- Vulnerabilities that only affect outdated or unpatched browser/plugin versions.
- Vulnerabilities requiring exceedingly unlikely user interaction.
- Vulnerabilities, such as timing attacks, that prove the existence of a user or site.
- Vulnerabilities requiring social or physical attacks.
- Reports related to denial of service attacks or DNSsec.
- Insecure cookie settings for non-sensitive cookies.
- Reports related to HTTP Digest authentication being better than HTTP Basic (it isn't)
- Reports related to password strength requirements
- Disclosure of public information and information that does not present significant risk.
- Vulnerabilities that have already been submitted by another user, that we are already aware of, or that have been classified as ineligible.
- Scripting or other automation and brute forcing of intended functionality.
- Issues that we can't understand or reproduce.
Commonly False Positive Reports
- BrickFTP is an FTP, SFTP, and WebDAV hosting service. Obviously this means that we will have an open FTP server on port 21, SFTP on port 22, and it means that our servers respond to DAV verbs.
Reporting any of the above false positives shall result in your being
blacklisted from the Program.
We aim to pay bounties as quickly as possible and will pay bounties sometimes
before the issue is patched. Therefore, we require that you do not disclose
any vulnerability publicly, either before or after the bounty is paid.
If paid a bounty, you may disclose that you received a bounty, but you may not
disclose the amount or any information related to the type of vulnerability
you found. Under no other circumstances may you disclose anything about your
participation in this program.
You are still bound by the Terms of Service you agreed to upon signup for your
Trial account. Please read and understand this document as it affects your
To Report a Vulnerability
To report a vulnerability, first re-read this entire page to be sure that you
understand the terms. We may refuse to pay bounties if you violate the terms
on this page, even if we act on the submission.
We will respond as quickly as possible to your submission.