
Amazon Vulnerability Research Program - Devices
External Program
Submit bugs directly to this organization


External Program
Submit bugs directly to this organization
Safeguarding our customers’ security is a top priority. We recognize that performing high quality security research requires considerable amount of effort, time, and skills investment from researchers. We value the contributions of external security researchers who help bring potential issues to our attention and further protect our customers/improve the security of our devices and services. The Amazon Devices and Services bug bounty program is designed to recognize security research on our consumer electronics - Fire branded devices and tablets, Echo, Kindle, Blink, Alexa, and Luna Gaming devices, associated cloud services and web/mobile applications through bounty rewards. If you believe you have discovered a vulnerability impacting our devices and services, we encourage you to report it to us through this portal. Please review this page for our process, responsible research and disclosure policy, reward guidelines, and detailed scope of The Amazon Devices and Services Bug Bounty Program.
In order to be eligible for a bounty reward, you must be the first to report an issue to us for assets outlined in scope. To ensure appropriate reward allocations, please provide a detailed report including - software version of device/application research was performed on, clear description of the issue, proof of concept (wherever applicable), along with detailed steps to reproduce the issue; you can optionally also provide patch/mitigation suggestions. We will acknowledge the receipt of the report, and in case of any additional questions, we will communicate and work with you through the HackerOne portal. To be considered for a reward, you must comply with all parts of this policy, including the following requirements -
Please note that we will prioritize the remediation of the submissions based on the risk, customer impact, severity of the issue reported.
To be eligible for the program, you must not:
Contact Us based functionality.If you find a bypass of a previous report you’ve created, or we ask that you create a new report due to the content being different enough, please fill out the Custom Field Bypass Reference with the original ID of the finding. This has no bearing on reward, it just helps Amazon with secondary data tracking.
Please create accounts using a HackerOne email to help us track security research activity. You can create accounts on Amazon by using [email protected]
Also, while testing please forward the string amazonvrpresearcher_yourh1username in your User-Agent header. You can create match and replace proxy rule in Burp by going to Proxy >> Options >> Match and Replace with the following options:
Type: Request header
Match: ^User-Agent.*$
Replace: User-Agent: amazonvrpresearcher_yourh1username
In Scope Devices This program sponsors the vulnerabilities discovered on devices (listed below) that are running latest available software.
Software Update Reference
In Scope Services & Apps In Scope Mobile Application Packages:
| Name | Android Package Name | Apple iOS App ID |
|---|---|---|
| FreeTime | com.amazon.tahoe.freetime | 1324809509 |
| Alexa Companion App | com.amazon.dee.app | 944011620 |
| FireTV (Bison) | com.amazon.storm.lightning.client.aosp | 947984433 |
| Kindle | com.amazon.kindle | 302584613 |
| Amazon Photos | com.amazon.clouddrive.photos | 621574163 |
| Amazon Key | com.amazon.cosmos | 1291586307 |
| Amazon Luna | com.amazon.tails | 1528364633 |
==(Note: Reports on outdated version/builds are out of scope)==
In Scope Web Applications Domains:
| Name | Domain |
|---|---|
| Alexa Developer | developer.amazon.com/alexa/* |
| Amazon App Store | developer.amazon.com/apps-and-games/* |
| Alexa Web | alexa.amazon.com |
| Skills Store | skills-store.amazon.com |
| Kindle Cloud Reader | read.amazon.com |
| Kindle Publishing | https://kdp.amazon.com |
| Alexa Answers | alexaanswers.amazon.com |
| Alexa BluePrints | blueprints.amazon.com |
| Amazon FireTV App Creator | creator.amazon.com |
| Device Content Manager | amazon.com/hz/mycd/* |
| Amazon Photos | https://www.amazon.com/photos/ |
| Amazon Luna | https://luna.amazon.com/ |
| Alexa API | https://api.amazonalexa.com/ |
The severity of a vulnerability generally reflects the security impact of the issue on the product. Please use the following description to determine the severity of reported issues. Please note there maybe additional vulnerabilities that are not explicitly called out in the below description. In all cases, Amazon reserves the sole discretion to determine the severity of the vulnerability based on security impact.
The Severity mentions below are a guideline, and not definitive. There may be situations where compensating controls or complexity of a finding increases or decreases severity.
Reports of zero-day vulnerabilities (vulnerabilities that were not previously known to the security community) within in-scope services and products will be eligible for an award at our discretion if the report provides significant insight that assists Amazon's security teams with remediation efforts, or has not previously been identified by another researcher on our own vulnerability response program.
Severity Rating for Devices Note, issues that are demonstrated with ADB are generally accepted only if ADB is used to demonstrate a behavior that is possible to implement in an app.
Critical Critical vulnerabilities may allow a remote attacker to gain control of the device or cause a permanent, unrecoverable device failure even after factory reset. Vulnerabilities that allow an attacker to perform remote or local bypass of critical security controls for example secure boot bypass fall into this category. Vulnerabilities that allow an attacker to perform arbitrary code execution, or remote access to sensitive assets on the device for example a device owner’s Amazon account credentials or authentication tokens, are also classified as critical vulnerabilities.
High High vulnerabilities may allow temporary bypass of critical security controls through local access. This category includes vulnerabilities that could allow arbitrary code execution in an unprivileged process or local code execution in a privileged process with user interaction. Vulnerabilities that could allow local access to owner’s Amazon account or other sensitive data protected by device kernel or a privileged process fall into this category. Vulnerabilities that allow bypass of core security features such as mandatory access controls, sandboxing mechanisms or bypass user interaction requirements for device operations example, modifying privacy settings, or installing apps. Additionally, these vulnerabilities may include device bricking scenarios such as vulnerabilities that cause permanent, unrecoverable device failure even after factory reset with local access vector, and vulnerabilities that cause temporary device failure requiring a factory reset with remote access vector.
Medium Medium vulnerabilities may allow a local attacker to cause temporary device failure requiring a factory reset with local access vector. Protocol security weaknesses that allow observing of sensitive information through physical access are included in this category. Vulnerabilities that allow bypassing of exploit mitigations would also fall into this category. These vulnerabilities could have similar impact to High vulnerabilities but may require other vulnerabilities or user interaction.
Low Low vulnerabilities that may not pose a direct security impact to customer or the device such as parental control bypasses.
Please note that any reports related to the prompt response content are out of scope where there is no clear application security impact and the potential issue is about responsible AI usage. We will not reward on these reports and close them as informative unless there is direct application security impact on the in-scope GenAI applications. Few examples for these out-of-scope reports are generation of inappropriate text/visual content with the model, get inappropriate suggestions from the model, malicious code generation. Any issues which are result of model hallucinations are out scope as well.
IMPORTANT NOTE: DO NOT submit generated sensitive images such as sexually explicit images, extremely graphic or violent images, or Child Sex Abuse Material (CSAM) in reports. Amazon Bug Bounty will not review this material or reward it, and your account may be banned.
| Potential Vulnerabilities | Severity | Comments |
|---|---|---|
| Unauthorized access/disclosure of PII/PHI data | High-Critical | Severity will be dependent on the context and influencing factors. |
| Cross customer sensitive data access | High-Critical | Severity will be dependent on the context and influencing factors. |
| Unauthorized system or environment changes | High-Critical | Severity will be dependent on the context and influencing factors. |
| Model Theft and LLM training data poisoning | High-Critical | Depending on the overall impact and application context. |
| Advarsaries can retrieve personal customer data without consent | High-Critical | Severity will be dependent on the context and influencing factors. |
| Information Disclosure | Low-Critical | Severity will be dependent on the context and influencing factors. |
| Prompt Injection | Medium - Critical | Severity will be dependent on the context and influencing factors. Please make sure to read notes above |
| Insecure Output Handling | Medium-Critical | Impact will depend on resulting potential vulnerabilities like HTML injection,XSS,SSRF, RCE etc. |
| Insecure plugins impacting models | Medium-High | Depending on the impact like content injection, code execution, differential error responses, system data exfiltration, |
| Excessive functionality, permissions and autonomy | Low-High | Depending on the actions allowed by excessive agency issues |
| Response manipulation providing guidance to customers | Medium-High | Severity will be dependent on the context and the guidance. |
| Adversaries can perform unauthorized actions on behalf of users | Medium-Critical | Depending on the impact, ease and issue radius. |
| LLM vulnerable to solicitation and social engineering | Medium-High | Depending on the overall impact and application context. |
| In context data could be used to de-anonymize users | Medium | Severity will be dependent on the context and influencing factors. |
| Absent customer API or data opt out mechanisms | Medium | Severity will be dependent on the context and influencing factors. |
| Command Injection | High-Critical | Depending on the impact, ease and issue radius. |
| API Auth Bypass | High-Critical | Depending on the impact, ease and issue radius. |
| Runtime Information Disclosure | Low-Medium | Severity will be dependent on the context and influencing factors. |
Service & Apps Vulnerability Severity Ratings Use following table to determine the severity ratings for web and mobile app vulnerabilities.
| Vulnerability | Severity Range |
|---|---|
| Remote Code Execution | Critical |
| SQL Injection | High - Critical |
| XXE | High - Critical |
| XSS | Medium - High |
| Server-Side Request Forgery | Low - Critical |
| Directory Traversal - Local File Inclusion | Medium - High |
| Authentication/Authorization Bypass (Broken Access Control) | Medium - High |
| Privilege Escalation | Medium - High |
| Insecure Direct Object Reference | Medium - Critical |
| Misconfiguration | Low - High |
| Web Cache Deception | Low - Medium |
| CORS Misconfiguration | Low - Medium |
| CRLF Injection | Low - Medium |
| Cross Site Request Forgery | Low - Medium |
| Open Redirect | Low - Medium |
| Information Disclosure | Low - Medium |
| Request smuggling | Low – Medium |
| Mixed Content | Low |
The goal of this program is to improve the security of our services for Customers. We do not reward, but will accept “Operational Security” (OpSec) submissions. OpSec issues include leaked employee passwords, password dumps, leaked business documents, etc. These submissions will only receive reputation points.
By participating in this program, you agree not to share publicly or privately any details or descriptions of your findings with any party. We require that you -
While it is our goal to resolve the vulnerabilities reported to us in responsible timeframe, the vulnerabilities initially disclosed publicly or to a third party without our consent may not be eligible for rewards.
Amazon will not bring any legal action against anyone who makes a good faith effort to comply with program policies, or for any accidental or good faith violation of this policy. This includes any claim under the Digital Millennium Copyright Act (DMCA) for circumventing technological measures to protect the services and applications eligible under this policy. As long as you comply with this policy:
Amazon cannot authorize any activity on third-party products or technology (including any third-party technology that is included in, or that interoperates with, Amazon products) or guarantee that third parties won’t pursue legal action against you. We aren’t responsible for your liability from actions performed on third parties or their technology. Don’t do anything illegal or unethical. You are responsible for complying with local laws, restrictions, regulations, etc. To protect your privacy, we will not, unless served with legal process or to address a violation of this policy: