Vulnerability Disclosure Policy

Security is core to our values, and we value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Expectations

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

Extend Safe Harbor (see below) for your vulnerability research that is related to this policy;
Work with you to understand and validate your report, including a timely initial response to the submission (usually within one business day);
Work to remediate discovered vulnerabilities in a timely manner; and
Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.

Ground Rules

To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you:

Play by the rules. This includes following this policy, as well as any other relevant agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail;
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 Channel (see below) to discuss vulnerability information with us;
Keep the details of any discovered vulnerabilities confidential until we’ve had at least 90 days to resolve the issue or until they are fixed;
Perform testing only on systems in the Scope of this policy (see below), 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) or proprietary information;
Do not engage in extortion.

Safe Harbor

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

Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar national or state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Exempt from national implementations of the WIPO Copyright Treaty (such as the Digital Millennium Copyright Act in the US), and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and
Lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through our Official Channel (see below) before going any further.

Scope

The scope of this policy covers:

Our web site and other Internet resources in the domain obdev.at;
All software which can be downloaded from servers in the domain obdev.at

Explicitly not in the scope of this policy are third party services such as our payment processors unzer.com and paypal.com.

CVE Numbers

We, Objective Development, are a CVE Numbering Authority (CNA) for the scope of our own products and services as outlined under "Scope" above. This means that all information about vulnerabilities of these products and services must be directed to our Official Channel (see below).

If we acknowledge the issue you report as a vulnerability, we assign a CVE number. The number and associated data is kept secret until either (a) the issue is fixed and customers have been given time to upgrade, or (b) the issue has become public.

Official Channel

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing security@obdev.at. Please include the following details with your report:

Description of the location and potential impact of the vulnerability;
A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
Your name/handle and a link for recognition in release notes.

If you’d like to encrypt the information, please use our PGP key:

Acknowledgements

This Vulnerability Disclosure Policy is based in part on documents provided by disclose.io and Bugcrowd.