Vulnerability Disclosure Policy

Introduction

Security of user data and communication is of utmost importance to Pudding. In pursuit of the best possible security for our service, we welcome responsible disclosure of any vulnerability you find in Pudding. Principles of responsible disclosure include, but are not limited to:

• Accessing or exposing only customer data that is your own.
• Avoiding scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site).
• Keeping within the guidelines of our Terms Of Service.
• Keeping details of vulnerabilities secret until Pudding has been notified and had a reasonable amount of time to fix the vulnerability.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly, and Pudding App will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Under this policy, “research” means activities in which you:

• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
• Do not submit a high volume of low-quality reports.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Test methods

The following test methods are not authorized:

• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing
• Possibilities to send malicious links to people you know
• Security bugs in third-party websites that integrate with Pudding
• Mixed-content scripts on www.success.app
• Insecure cookies on www.success.app
• Social engineering attacks against Pudding Support
• Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves be susceptible

Scope

This policy applies to the following systems and services:

• www.success.app
• my.www.success.app

Any service not expressly listed above, are excluded from scope

If you aren’t sure whether a system is in scope or not, contact us at [email protected] before starting your research.

Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.

Reporting a vulnerability

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. We will not share your name or contact information without express permission.

We accept vulnerability reports via [email protected]. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.

What we would like to see from you

In order to help us triage and prioritize submissions, we recommend that your reports:

• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps including the url needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).

What you can expect from us

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

• Within 3 business days, we will acknowledge that your report has been received.
• To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
• We will maintain an open dialogue to discuss issues.

Questions

Questions regarding this policy may be sent to [email protected]. We also invite you to contact us with suggestions for improving this policy.