Envestnet | Yodlee Security Office

Submit Vulnerability Report

We Want Security Researchers to Feel Comfortable Reporting Vulnerabilities

Envestnet is committed to ensuring security by protecting information from unwarranted disclosure. This program is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

This document provides guidelines on scope of the program, how to report, and timelines for public disclosure.

We want security researchers to feel comfortable reporting vulnerabilities they’ve discovered – as set out in this document – to enable us remediate the issues and protect the Envestnet ecosystem. We have developed this program to reflect our values and uphold our sense of responsibility to security researchers who share their expertise with us in good faith.

Guidelines

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Do not retain, transfer or otherwise access sensitive information after initial discovery. Any sensitive information that has been obtained accidentally or otherwise must be returned promptly and any copies must not be retained.
  • 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.
  • 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.
  • Do not submit a high volume of low-quality reports.

Program Scope and Rules

If you make a good faith effort to comply with this program during your security research, we will work with you to understand and resolve the issue quickly, and Envestnet will not recommend or pursue legal action related to 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 program over time.

We are interested in information about vulnerabilities in the following categories:

  • Injection.
  • Cross-site scripting.
  • Password management.
  • Data transmission.
  • Misconfigured systems that allow unintended access to systems and information.

The following categories are not in scope of the program and must not be attempted:

  • Network denial of service (DoS or DDoS) tests.
  • Physical testing (e.g. office access, open doors, tailgating), or any other non-technical vulnerability testing.
  • Tests against Cloud Service Providers where no Vulnerability Disclosure Policy exists.
  • Phishing or Social Engineering.
  • Third party services or systems used by Envestnet. Any activity by a researcher residing in a country on a United States sanctions list.

How to Report

To report a vulnerability please click here.

Information submitted under this program will be used for defensive purposes only – to mitigate or remediate vulnerabilities.

We will acknowledge receipt of your report within 3 business days.

All reports are considered confidential until otherwise specified. We request 90 days from Envestnet’s initial acknowledgment of the report prior to making the report public.

What we would like to see from you

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

  • Report of the discovered vulnerability as soon as it is feasible once it has been validated.
  • Describe the vulnerability, where it was discovered, and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
  • English preferred, if possible.

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.