Vulnerability Disclosure Policy

We value and thank 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.

Definition of a Vulnerability

Safe Software considers a security vulnerability to be a weakness in one of our products or infrastructure that could allow an attacker to impact the confidentiality, integrity, or availability of the product or infrastructure.

We do not consider the following types of findings to be security vulnerabilities. The following is a partial list of issues that we ask for you not to report, unless you believe there is an actual vulnerability:

• Presence or absence of HTTP headers (X-Frame-Options, CSP, nosniff, etc.). These are considered security best practices and therefore we do not classify them as vulnerabilities.
• Phishing or social engineering techniques.
• Vulnerabilities only affecting users who are using outdated or unpatched browsers and platforms.
  Sender Policy Framework (SPF) configuration suggestions.
• Domain Name System Security Extensions (DNSSEC) configuration suggestions.

Systems in Scope

This policy applies to any software products, digital assets and services owned, developed, operated, or maintained by Safe Software.

Out of Scope

• Assets, services or other equipment not owned by Safe Software.

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

When working with us according to this policy, you can expect us to:

• Respond to your report promptly, and work with you to understand and validate your report;
• Strive to keep you informed about the progress of a vulnerability as it is processed;
• Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
• Extend Safe Harbor for your vulnerability research that is related to this policy.

Our Request

In participating in our vulnerability disclosure program in good faith, we ask that you:

• Report any vulnerability you’ve discovered promptly;
• Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
• Use only the official channels (see below) to discuss vulnerability information with us;
• Keep potential vulnerabilities confidential until we are able to address them;
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly;
• Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
• If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), credit card data, or proprietary information;
• Securely delete all data retrieved during your research as soon as it is no longer required or within one month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law);
• Refrain from using automated tools to report vulnerabilities, unless you have manually verified the vulnerability;
• Do not perform denial-of-service (DoS) or distributed denial-of-service (DDoS) attacks;
• Only interact with test accounts you own or with explicit permission from the account holder; and
  Do not engage in extortion.

Official Channels

Please report security issues, providing all relevant information, using the following email: security at safe dot com. If you are a current customer, please create a Support Case. If you purchased FME through a Partner, please contact them directly.

The more details you provide, the easier it will be for us to triage and fix the issue. In your report, please include details of:

• Type of issue (cross-site scripting, SQL injection, remote code execution, etc.);
• Product and version with the bug or a URL if dealing with a cloud service;
• The potential impact of the vulnerability (i.e. what data can be accessed or modified);
• Step-by-step instructions to reproduce the issue; and
• Any proof-of-concept or exploit code required to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

What to Expect

After you have submitted your report, Safe’s Security and Product Development team will investigate and verify the vulnerability. We will aim to triage and respond to your report within a reasonable period. We’ll also endeavor 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. 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 reported vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us.

Submission License

Communications between you and Safe Software, including emails you send to Safe Software reporting a potential security vulnerability, should not contain any of your proprietary information. By submitting any information, you are granting Safe Software a perpetual, royalty-free and irrevocable right and license to use, reproduce, modify, adapt, publish, translate, distribute, transmit, publicly display, publicly perform, sublicense, create derivative works from, transfer and sell such information.

Safe Software will not disclose your personal information without your written consent, but may otherwise use such communication or material for any purpose whatsoever, including, but not limited to, reproduction, disclosure, transmission, publication, broadcast, and further posting. Further, Safe Software is free to use any ideas, concepts, know-how, or techniques contained in any communication or material you send to Safe Software for any purpose whatsoever, including, but not limited to, fixing, developing, manufacturing, and marketing products.

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

• Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
• Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
• Exempt from restrictions in our FME Software License Agreement, FME Flow Hosted Terms of Use, and other Safe Software Terms of Use that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
• Lawful, helpful to the overall security of the FME community, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
Note that the Safe Harbor applies only to legal claims under the control of Safe Software, and does not bind independent third parties.