No technology is perfect, and Teradici 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 issue in our product or
service, we encourage you to notify us. We welcome working with you to resolve
the issue promptly.
- Teradici's Product Security Team will acknowledge your report, usually within 72 hours.
- Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
- Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
- When our Team resolves the issue, we will post an update along with thanks and credit for the discovery.
- 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.
While researching, we'd like to ask you to refrain from:
- Teradici webdomains (website, customer support and forum sites, etc) is out of scope.
- www.teradici.com __or any other web domains are NOT the target. Please see the next section for target products.
- Teradici IT infrastructure
- Denial of service
- Social engineering (including phishing) of Teradici staff or contractors
- Any physical attempts against Teradici property or data centers
- Other Teradici or partner products that is not in scope. For example, PCoIP Zero Client, PCoIP Client Software, VMware View Horizon, Amazon Workspace, etc are out of scope.
Currently Teradici does not offer bounty at this moment. However a critical
vulnerability reported may be paid out at our discretion, depending on the
budget at hand, as a display of sincere thanks.
Scope - Target Products
We would like your help with the following products
1) Management Console 2 __
2) Cloud Access Software __
About Cloud Assess Software __
You can deploy an instance on any public cloud infrastructure. You can set up your test environment with 60 days trial period license. Security vulnerabilities arising from OS platform configuration is out of scope. What is in scope is the Cloud Access Software binaries and processes that gets deployed on a given host machine.
Here is the Trial sign up page __
When you sign up for a demo trial, Please specify Company, Department type as other, and in the "tell us about your project" section, please mention about the bounty program.
Out of scope (some examples, please edit to your company)
- Unauthenticated CSRF
- Logout CSRF
- Attacks requiring 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.
- Disclosure of software version numbers
- Vulnerabilities that require social engineering/phishing
- HTTP 404 codes/pages or other HTTP non-200 codes/pages.
- Fingerprinting / banner disclosure on common/public services.
- Disclosure of known public files or directories, (e.g. robots.txt).
- Clickjacking and issues only exploitable through clickjacking.
- CSRF on forms that are available to anonymous users (e.g. login or contact form).
- Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality.
- Lack of Security Speedbump when leaving the site.
- No Captcha / Weak Captcha / Captcha Bypass
- Login or Forgot Password page brute force and account lockout not enforced
- OPTIONS HTTP method enabled
- WebServer Type disclosures
- Social engineering of our service desk, employees or contractors
- Error messages with non-sensitive data
- Non-application layer Denial of Service or DDoS
- Lack of HTTP Only / SECURE flag for cookies
- Username / email enumeration via Login Page error message or via Forgot Password error message
- Missing HTTP security headers, specifically (https://www.owasp.org/index.php/List_of_useful_HTTP_headers __), e.g. Strict-Transport-Security, X-Frame-Options, X-XSS-Protection, X-Content-Type-Options, Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP, Content-Security-Policy-Report-Only
- SPF / DMARC / DKIM Mail and Domain findings
- DNSSEC Findings
- CSV Issues
- AV Scanning
- SSL Issues, e.g. SSL Attacks such as BEAST, BREACH, Renegotiation attack, SSL Forward secrecy not enabled SSL weak / insecure cipher suites
- In order to qualify as a valid vulnerability, it must exist in the latest version that is publicly available on our website.