DYMO Vulnerability Disclosure Policy


This policy describes how customers and security researchers report vulnerabilities to DYMO (“DYMO”, “we”, ”us” or “our”) and our support.

Scope of vulnerability report

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us, including products, software, cloud services. We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.
We do not accept reports for the following:
  • Unsupported products
  • Non-reproducible and previously disclosed vulnerabilities
  • Denial of service vulnerabilities
  • Non-exploitable vulnerabilities
  • Social Engineering Attacks
  • Security Bugs in third party websites

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.

Reporting a vulnerability

If you believe you have found a security vulnerability, please submit your report to us using the following email: [email protected];
In your report please include:
Product name, software version and functionality/network protocol where vulnerabilities have been discovered.
Potential impact if vulnerabilities are exploited.
A detail description of the steps to reproduce the vulnerability.

Our response after receiving a report

After you have submitted your report, we will respond to your report within 10 working days and aim to triage your report within 60 working days. We will also aim to keep you informed of our progress.
Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 10 days. This allows our teams to focus on the remediation.
We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.
Once your vulnerability has been resolved, we welcome requests to disclose your report. We would like to unify guidance to affected users, so please do continue to coordinate public release with us.