Tide believes in keeping its members data secure and private. We acknowledge the valuable role that independent security researchers play in security and, as a result, we encourage responsible reporting of any vulnerabilities that may be found in our site or product. Tide welcomes feedback from the security community on its product, platform and website to help keep our business and members safe. If you have information related to security vulnerabilities discovered within Tide products and services, please submit a report in accordance with our Responsible Disclosure Policy.
Our Responsible Disclosure Policy allows for security testing to be conducted by anyone in the security community with safe communication of those results. If any vulnerabilities are identified please report them to Tide at email@example.com using the following PGP to encrypt the message and any attachments:
We welcome your support to help us address any security issues, both to improve our products and protect our members.
What we would like to see from you:
Your reports will be reviewed and validated by a member of the Tide Security team. Providing clear and concise steps to reproduce the issue will help to expedite the response. As a minimum, your report must include:
Clear description and evidence of the vulnerability (logs, screenshots, responses)
Any platforms, operating systems, versions that are relevant
Any relevant IP addresses, URLs and parameters
Any supporting evidence you have collected (logging, tracing etc.)
Your name, contact details and other personal details on our request
Please preserve as much evidence as possible.
Describe the impact. How would the vulnerability be exploited?
Steps to reliably reproduce the issue.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider both the attack scenario/exploitability and the impact of the vulnerability. The following issues are considered out of scope:
Reports from automated tools or scans
Reports affecting outdated browsers
Denial of Service Attacks
Missing best practices in Content Security Policy.
Issues without clearly identified security impact or speculative theoretical exploitability
Missing security best practices and controls (rate-limiting/throttling, lack of CSRF protection, lack of security headers, missing flags on cookies, descriptive errors, server/technology disclosure – without clear and working exploit)
Lack of crossdomain.xml, p3p.xml, robots.txt or any other policy files and/or wildcard presence/misconfigurations in these.
Lack of HTTPS
Reports about insecure SSL / TLS configuration
Password complexity requirements, account/email enumeration, or any report that discusses how you can learn whether a given username or email address has a Tide related account
Presence/Lack of autocomplete attribute on web forms/password managers.
Server Banner Disclosure/Technology used Disclosure
Full Path Disclosure
IP Address Disclosure
Publicly accessible login panels
CSS Injection attacks. (Unless it gives you the ability to read anti-CSRF tokens or other sensitive information)
Host Header Injection (Unless it gives you access to interim proxies)
Reflective File Download
Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin: * or accepting of custom Origin header that does not specifically show a valid attack scenario
PRSSI – Path-relative stylesheet import vulnerabilities (without an impactful exploitation scenario – for example stealing CSRF-tokens)
OPTIONS/TRACE/DELETE/PUT/WEBDAV or any other HTTP Methods accepted by the server which do not specifically show a valid attack scenario
Cookie scoped to parent domain or anything related to the path misconfiguration and improperly scoped
Private IP/Hostname disclosures or real IP disclosures for services using CDN
Open ports that do not lead directly to a vulnerability
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Lack of DNS CAA and DNS-related configurations
Weak Certificate Hash Algorithm
Social engineering of Tide employees or contractors
Any physical/wireless attempt against Tide property
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Open redirect – unless an additional security impact can be demonstrated
Issues that require unlikely user interaction
For the avoidance of doubt, any such report, incl. security vulnerabilities discovered that are not in compliance with this responsible disclosure policy, will deem proprietary rights of Tide and Tide will own all intellectual property rights there of with no liability nor whatsoever to the reporter. By submitting any such report, the reporter explicitly understands and agrees to this provision. This responsible disclosure policy is dated 1st October 2020 and may be periodically updated per Tide’s sole discretion. Therefore, please bookmark this page and check whether newest version of the policy is available prior to taking any action.