Vulnerability Detection Policy

Vulnerability Detection

If you have information related to security vulnerabilities of Yodeck, we want to hear from you. Please submit a report in accordance with the guidelines below. We value the positive impact of your work and thank you in advance for your contribution.

We will offer a reward of up to $100, depending on severity, to people who submit vulnerability detection reports that adhere to the guidelines and scope defined below in this page and are assessed to be valid by the Yodeck security team.


Yodeck agrees to not pursue claims against researchers related to the disclosures submitted through this website who:

  • do not cause harm to Yodeck, our customers, or others;
  • provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);
  • do not compromise the privacy or safety of our customers and the operation of our services;
  • do not violate any law or regulation;
  • publicly disclose vulnerability details only after Yodeck confirms completed remediation of the vulnerability and not publicly disclose vulnerability details if there is no completion date or completion cannot be ascertained;
  • confirm that they are not currently located in or otherwise ordinarily resident in Cuba, Iran, North Korea, Syria or Crimea; and
  • confirm that they are not on the U.S. Department of the Treasury’s Specially Designated Nationals List.

Out of Scope

Yodeck agrees to not pursue claims against researchers related to the disclosures submitted through this website who:

  • Reports from automated tools or scans
  • Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
  • Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
  • Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
  • Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
  • Self-exploitation (e.g., cookie reuse)
  • Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
  • Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a Yodeck-related account
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
  • Social engineering of Yodeck employees or contractors
  • Presence of autocomplete attribute on web forms
  • Missing secure cookie flags on non-sensitive cookies
  • Denial of Service Attacks
  • Banner identification issues (e.g., identifying what web server version is used)
  • Open ports which do not lead directly to a vulnerability
  • Open redirect vulnerabilities
  • Publicly accessible login panels
  • Clickjacking
  • Content spoofing / text injection
  • Tabnabbing
  • Rate-limit vulnerabilities

In order to submit your vulnerability findings report please contact us at security at yodeck dot com. By contacting us, you consent to your information being transferred to and stored in the EU and acknowledge that you have read and accepted the Terms of Use and Privacy policy of Yodeck.