Vulnerability Disclosure Program Policy
Adobe recognizes that the security community is a force multiplier in our quest to provide a safe and secure experience for Adobe’s customers. To that end, we welcome the contributions of security researchers and strive to provide the best vulnerability disclosure experience possible.
Table of Contents
- Response Targets
- Eligible Vulnerabilities
- Program Exclusions
- Safe Harbor
- Terms and Conditions
Adobe makes every effort to meet the following SLAs for hackers participating in our program:
|Type of Response
|SLA in business days
|Time to Triage
|Time to Resolution
|dependent on severity and complexity
We’ll try to keep you informed about our progress throughout the process.
Your submission will be reviewed and validated by a member of the Product Security Incident Response Team.
- When submitting a vulnerability, please provide concise steps to reproduce that are easily understood.
- Including a proof-of-concept for desktop vulnerabilities will expedite our investigation. We encourage you to use PGP encryption (key here).
- If the same vulnerability is found on multiple hosts associated with the same asset/domain, please include all vulnerable hosts in a single report.
- When duplicates occur, we consider the first report that was received to be treated as unique, and subsequent reports will be marked as a duplicate.
We encourage disclosure of any security vulnerabilities that have the potential to impact the security or privacy of our customers. When submitting a vulnerability report, please provide concise steps to reproduce that are easily understood.
In the interest of fostering coordinated disclosure, Adobe will collaborate with finders in good faith who wish to disclose vulnerabilities. To protect our customers, we expect that finders will wait until a fix has been made available and communicated to impacted customers, or a reasonable period of time has elapsed since notification.
This program does not provide monetary rewards for bug submissions.
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Terms and Conditions
- Please use your own account for testing or research purposes. Do not attempt to gain access to another user’s account or confidential information.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
- Please do not test for spam, social engineering, or denial of service issues.
- Please do not engage in any activity that can potentially or actually cause harm to Adobe, our customers, or our employees.
- Do not engage in any activity that violates (a) federal or state laws or regulations or (b) the laws or regulations of any country where (i) data, assets, or systems reside, (ii) data traffic is routed, or (iii) the researcher is conducting research activity.
- Do not store, share, compromise, or destroy Adobe or customer data. If Personally Identifiable Information (PII) is encountered, you should immediately halt your activity, purge related data from your system, and immediately contact Adobe. This step protects any potentially vulnerable data, and you.