RESPONSIBLE DISCLOSURE POLICY
Hostinger encourages the responsible disclosure of security vulnerabilities in our services or on our website. In order to facilitate the responsible disclosure of security vulnerabilities, we agree that if, in our sole discretion, we conclude that a disclosure meets all of the guidelines of the Hostinger Bug Bounty Reward Program, Hostinger will not bring any private or criminal legal action against the disclosing party.
BUG BOUNTY REWARD PROGRAM POLICY AND TERMS
Our team of dedicated security professionals works vigilantly to help keep customer information secure. We recognize the important role that security researchers and our user community play in helping to keep Hostinger and our customers secure. If you discover a site or product vulnerability please notify us using the guidelines below.
Please note that your participation in the Bug Bounty Program is voluntary and subject to the terms and conditions set forth on this page (“PROGRAM TERMS”). By submitting a site or product vulnerability to Hostinger you acknowledge that you have read and agreed to these PROGRAM TERMS.
As part of your research, do not modify any files or data, including permissions, and do not intentionally view or access any data beyond what is needed to prove the vulnerability.
THE FOLLOWING HOSTINGER DOMAINS IN SCOPE:
Please note that www.hostinger.com and www.hosting24.com is using the same code base, so vulnerability found on one domain will be treated as duplicate on another.
Domains not listed above are not in scope.
Hostinger will make a best effort to adhere to the following response targets:
|Type of Response||Business days|
|First Response||2 working days|
|Time to Triage||10 working days|
|Time to Bounty||14 working days|
|Time to Resolution||depends on severity and complexity|
To be eligible for the Bug Bounty Program, you must not:
- Be in violation of any national, state, or local law or regulation;
- Be employed by Hostinger or its subsidiaries;
- Be an immediate family member of a person employed by Hostinger or its subsidiaries or affiliates; or
- Be less than 16 years of age. If you are at least 16 years old, but are considered a minor in your place of residence, you must get your parent’s or legal guardian’s permission prior to participating in the program.
- If Hostinger discovers that you meet any of the criteria above, Hostinger will remove you from the Bug Bounty Program and disqualify you from receiving any Bounty Payments.
By providing a Submission or agreeing to the PROGRAM TERMS, You agree that you may not publicly disclose your findings or the contents of your Submission to any third parties in any way without Hostinger's prior written approval.
Failure to comply with the PROGRAM TERMS will result in immediate disqualification from the Bug Bounty Program and ineligibility for receiving any Bounty Payments.
Hostinger will accept a report of any vulnerability that substantially affects the confidentiality or integrity of any eligible Hostinger service. Eligible vulnerabilities include, but are not limited to:
- Authentication or authorization flaws, including insecure direct object references and authentication bypass
- Server-side or remote code execution (RCE)
- Injection vulnerabilities, including SQL and XML injection
- Directory Traversal
- Privilege Escalation
- Disclosure of sensitive or personally identifiable information
- Significant security misconfiguration with a verifiable vulnerability
- Exposed system credentials, disclosed by Hostinger or its employees, that pose a valid risk to an in scope asset
Any domain not listed in policy scope is out of scope for the purposes of the Bug Rewards Program, as is all hosted customer content and third-party programs and plug-ins.
The following actions do not qualify for the Bug Rewards Program and should not be tested by researchers participating in the Program:
- Reports that involve a secondary user account where an existing business relationship is being leveraged and the impact is limited solely to the parent account
- Username enumeration on customer facing systems (i.e. using server responses to determine whether a given account exists)
- Scanner output or scanner-generated reports, including any automated or active exploit tool
- Man-in-the-Middle attacks
- Any physical attacks against Hostinger property or data centers
- Cross Site Scripting (XSS)
- Cross Site Request Forgery (CSRF)
- Vulnerabilities involving stolen credentials or physical access to a device
- Phishing attacks
- Social engineering attacks, including those targeting or impersonating internal employees by any means (e.g. customer service chat features, social media, personal domains, etc.)
- Open redirection, except in the following circumstances:
- Clicking a Hostinger-owned URL immediately results in an unexpected redirection and loss of sensitive data (e.g. session tokens, PII, etc)
- CRIME/BEAST attacks
- Logout CSRF
- Banner or version disclosures
- Missing SPF records
- Directory listing (unless sensitive data can be found)
- DoS, brute force, user enumeration or DDoS attacks
- Blackhat SEO techniques
- Any other submission determined to be low risk, based on unlikely or theoretical attack vectors, requiring significant user interaction, or resulting in minimal impact
- Vulnerabilities on third party libraries without showing specific impact to the target application (e.g. a CVE with no exploit)
- Exposed credentials that are either no longer valid, or do not pose a risk to an in scope asset
- Any bug that relies upon an outdated browser
- Infrastructure vulnerabilities, including:
- Issues related to SSL certificates
- DNS configuration issues
- Server configuration issues (e.g. open ports, TLS versions, etc.)
- Bugs requiring exceedingly unlikely user interaction.
- Insecure password complexity requirements
- Email verification/validation issues
- Quality and business logic bugs which do not pose real risk and do not impact business and customers in a way which could lead to unauthorised access to data or systems, also when there is no possibility to take advantage of the bug to cause some sort of damage to company systems or data.
- Vulnerabilities on individual clients infrastructure or virtual private servers (VPS), including websites, databases, etc.
BUG SUBMISSIONS REQUIREMENTS
For all submissions, please include:
- Full description of the vulnerability being reported, including the exploitability and impact
- Evidence and explanation of all steps required to reproduce the submission, which may include:
- Videos or Step by step screenshots
- Exploit code
- Traffic logs
- Web/API requests and responses
- Email address or user ID of any test accounts
- IP address used during testing
- For RCE submissions, see below
Failure to include any of the above items may delay or jeopardize the Bounty Payment
REMOTE CODE EXECUTION (RCE) SUBMISSIONS GUIDELINES:
Failure to meet the below conditions and requirements could result in a forfeiture of any potential Bounty Payment.
- Source IP address
- Timestamp, including time zone
- Full server request and responses
- Filenames of any uploaded files, which must include “bugbounty” and the timestamp
- Callback IP and port, if applicable
- Any data that was accessed, either deliberately or inadvertently
- Directly injecting benign commands via the web application or interface (e.g. whoami, hostname, ifconfig)
- Uploading a file that outputs the result of a hard-coded benign command
- Uploading files that allow arbitrary commands (i.e. a webshell)
- Modifying any files or data, including permissions
- Deleting any files or data
- Interrupting normal operations (e.g. triggering a reboot)
- Creating and maintaining a persistent connection to the server
- Intentionally viewing any files or data beyond what is needed to prove the vulnerability
- Failing to disclose any actions taken or applicable required information
You may be eligible to receive a monetary reward (“Bounty Payment”) if: (i) you are the first person to submit a site or product vulnerability; (ii) that vulnerability is determined to by a valid security issue by Hostinger's security team; and (iii) you have complied with all PROGRAM TERMS.
Bounty Payments, if any, will be determined by Hostinger, in Hostinger sole discretion. In no event shall Hostinger be obligated to pay you a bounty for any Submission. All Bounty Payments shall be considered gratuitous.
All Bounty Payments will be made in United States dollars (USD). You will be responsible for any tax implications related to Bounty Payments you receive, as determined by the laws of your jurisdiction of residence or citizenship.
Hostinger will determine all Bounty Payments based on the risk and impact of the vulnerability. The minimum bounty amount for a validated bug submission is $100 USD and the maximum bounty for a validated bug submission is $6000USD.
Hostinger Bug Bounty Team retains the right to determine if the bug submitted to the Bug Bounty Program is eligible. All determinations as to the amount of a bounty made by the Hostinger Bug Bounty Team are final. Bounty Payment ranges are based on the classification and sensitivity of the data impacted, ease of exploit and overall risk to Hostinger customers, Hostinger brand and determined to be a valid security issue by Hostinger's security engineers.
OWNERSHIP OF SUBMISSIONS
As a condition of participation in the Hostinger Bug Bounty Program, you hereby grant Hostinger, its subsidiaries, affiliates and customers a perpetual, irrevocable, worldwide, royalty-free, transferrable, sublicensable (through multiple tiers) and non-exclusive license to use, reproduce, adapt, modify, publish, distribute, publicly perform, create derivative work from, make, use, sell, offer for sale and import the Submission, as well as any materials submitted to Hostinger in connection therewith, for any purpose. You should not send us any Submission that you do not wish to license to us.
You hereby represent and warrant that the Submission is original to you and you own all right, title and interest in and to the Submission. Further, you hereby waive all other claims of any nature, including express contract, implied-in-fact contract, or quasi-contract, arising out of any disclosure of the Submission to Hostinger. In no event shall Hostinger be precluded from discussing, reviewing, developing for itself, having developed, or developing for third parties, materials which are competitive with those set forth in the Submission irrespective of their similarity to the information in the Submission, so long as Hostinger complies with the terms of participation stated herein.
In the event (i) you breach any of these PROGRAM TERMS or the terms and conditions of the Hostinger; or (ii) Hostinger determines, in its sole discretion that your continued participation in the Bug Bounty Program could adversely impact Hostinger (including, but not limited to, presenting any threat to Hostinger's systems, security, finances and/or reputation) Hostinger may immediately terminate your participation in the Bug Bounty Program and disqualify you from receiving any Bounty Payments. Please see our recommendations on the proper procedures for testing our applications.
Any information you receive or collect about Hostinger, Hostinger employees or any Hostinger customer through the Bug Bounty Program (“Confidential Information”) must be kept confidential and only used in connection with the Bug Bounty Program. You may not use, disclose or distribute any such Confidential Information, including, but not limited to, any information regarding your Submission and information you obtain when researching the Hostinger sites, without Hostinger's prior written consent. Any disclosure of Confidential Information outside of this requirement will result in immediate removal from the Program.
In addition to any indemnification obligations you may have under the Hostinger Agreements, you agree to defend, indemnify and hold Hostinger, its subsidiaries, affiliates and the officers, directors, agents, joint ventures, employees and suppliers of Hostinger, its subsidiaries, or our affiliates, harmless from any claim or demand (including attorneys’ fees) made or incurred by any third party due to or arising out of your Submissions, your breach of these PROGRAM TERMS and/or your improper use of the Bug Bounty Program.
CHANGES TO PROGRAM TERMS
The Bug Bounty Program, including its policies, is subject to change or cancellation by Hostinger at any time, without notice. As such, Hostinger may amend these PROGRAM TERMS and/or its policies at any time by posting a revised version on our website. By continuing to participate in the Bug Bounty Program after Hostinger posts any such changes, you accept the PROGRAM TERMS, as modified.
Soumettre un rapport