By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation times

We will strive to validate all submissions within the below timelines, once your submission has been verified by Intigriti.

Introduction

We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!

Focus Areas

• E-commerce Payment & order flows
• Authorization flaws in API & Microservices in the e-commerce environment
• Any e-commerce functionality which processes customer data

Critical Scenarios

• Mass customer data exposure: emails, addresses, phone numbers, order history, etc.
• Zero-click mass customer account takeover
• Remote Code Execution
• Unauthorized access to important infrastructure, databases, or backend systems
• Checkout/order process abuse (e.g. free or discounted products)

Leaked Credentials

We welcome security researchers to responsibly report any discovered publicly leaked credentials that could allow unauthorized access or exposure of sensitive information.

Below is a list of generic guidelines on which credentials will or won't accept in reports:

Cases with impact:

• Credentials providing administrative or high-privileged access to network infrastructure, servers, or critical applications
• Credentials providing admin access to high-priority web applications within AS Watson’s attack surface.
• Credentials exposing sensitive data of a large number of employees or customers
• Credentials belonging to service accounts with broad access

Cases without significant impact:

• Personal user credentials for non-critical applications (e.g. training platforms, corporate social media)
• Credentials external to AS Watson’s domains/infrastructure (ex. personal Gmail account for AS Watson applications)
• Credentials that cannot be accessed due to multi-factor authentication (MFA)
• Individual customer credentials (we can only advice customers to be careful with their passwords)

⚠️ Please note that we will evaluate the impact of credential-related reports and reserve the right to make final determinations on bounty eligibility and awards. Private or paid for leaked credentials are strictly out of scope.

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks aren't sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact
• CSRF for non-sensitive actions (example: adding or removing a product to a shopping cart or wishlist)

General

• Ratelimit on OTP Request. Avoid sending high number of OTP Requests.
• Brute force on Login, E-giftCards, Promo codes, Vouchers, user account registration
• Forgot password token requests being leaked to third parties
• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile

• Shared links leaked through the system clipboard
• No session timeout
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions
• Vulnerabilities that require physical access to the victim device have limited impact

This program follows Intigriti's triage standards based on the proof of concept.

AS Watson takes information security risks seriously and is committed to handling reported vulnerabilities in a fair, transparent, and consistent manner.

The severity of a reported vulnerability is determined through an internal assessment process that considers both technical impact and business context. While industry-standard scoring systems (such as CVSS) may be used as an input, the final severity rating may differ based on our evaluation of the specific circumstances in which the vulnerability exists.

Where can we get credentials for the app?

You can self-register on the e-commerce applications but please don’t forget to use your @intigriti.me address.