vidaXL Services - Open Bug Bounty Program

Rules

vidaXL Services

At vidaXL, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present. If you discover a vulnerability, we would like to know about it, so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

Scopes description

For us it is important, that our whole webshops are being checked extensively (like homepage, product listing pages, product detail page, cart page, myaccount pages, login page, checkout page, thank you page, etc. and the different functionalities on them (f.e. loyalty programme, payment service provider, etc). Please take into account the following rules:

Only use the following 3 EAN's when placing test orders 8718475559313 8718475616184 8718475719380 (f.e. www.vidaxl.xx/e/8718475559313) (in case of violation, no bounty can be awarded). These are product EANs for products you can use to test.

Note: not all EANs are available on all webshops, as assortment can be different per webshop.

Shared codebase disclaimer: All webshops in scope use the same code-base and backend. If a specific issue has already been found in another vidaXL shop the report will be regarded as a duplicate.

Salesforce Assets: For Salesforce assets, the following rules apply: https://help.salesforce.com/articleView?id=000356579&type=1&mode=1 Thank you for browsing our pages and helping protect our shop and our customers!

Program Rules

Testing Policy, Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on vidaXL Services Holding applications, servers, networks or infrastructure are strictly forbidden.
• Avoid tests that could cause degradation or interruption of our services.
• Do not use automated scanners or tools that generate large amount of network traffic
• Do not leak, copy, manipulate, or destroy any user data or files in any of our applications/servers.
• No vulnerability disclosure, full, partial or otherwise, is allowed.
• Make sure to apply hunting requirements policy (User-Agent, VPN...)

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and identified outside of our program’s scope, such as:

• Exposed credentials in/from an out-of-scope asset/source
• Sensitive information exposed in/from an out-of-scope asset/source

Also, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behavior (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees/service providers.

This excludes, but is not limited to:

• Stolen credentials gathered from unidentified sources (e.g. …)
• Exposed credentials that are not applicable on the program’s scope
• Exposed GitHub/GitLab (or similar) instance with no direct relation with our program’s scope
• Exposed secrets (e.g. API tokens/keys or other technical credentials) that are not directly related to the program’s scope
• Exposed PII on an out-of-scope asset

####To summarize our policy, you may refer to this table :

Important precautions and limitations

As a complement to the Program’s rules and testing policy :

• DO NOT alter compromised accounts by creating, deleting or modifying any data
• DO NOT use compromised accounts to search for post-auth vulnerabilities (they won’t be eligible anyway)
• DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
• In case of exposed credentials or secrets, limit yourself to verifying the credentials validity
• In case of sensitive information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of vidaXL Services Holding, however only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• The report must contain the following elements:
• Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and vidaXL Services Holding, and remediation advice on fixing the vulnerability
• Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
• Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
• You must not break any of the testing policy rules listed above
• You must not be a former or current employee of vidaXL Services Holding or one of its contractors.

Reward amounts are based on:

• Reward grid of the report's scope
• CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Out of scope

• All domains or subdomains not listed in the above list of 'Scopes'

Qualifying vulnerabilities

• SQL Injection (SQLi)
• Cross-Site Scripting (XSS)
• Remote Code Execution (RCE)
• Insecure Direct Object Reference (IDOR)
• Horizontal and vertical privilege escalation
• Authentication bypass & broken authentication
• Business Logic Errors vulnerability with real security impact
• Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
• Cross-Origin Resource Sharing (CORS) with real security impact
• Cross-site Request Forgery (CSRF) with real security impact
• Open Redirect

Non-qualifying vulnerabilities

• Broken Link/Social media Hijacking
• Tabnabbing
• Missing cookie flags
• Content/Text injections
• Clickjacking/UI redressing
• Denial of Service (DoS) attacks
• Recently disclosed CVEs (less than 30 days sinces patch release)
• CVEs without exploitable vulnerabilities and PoC
• Open ports or services without exploitable vulnerabilities and PoC
• Social engineering of staff or contractors
• Presence of autocomplete attribute on web forms
• Vulnerabilities affecting outdated browsers or platforms
• Self-XSS or XSS that cannot be used to impact other users
• Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
• SSL/TLS issues (e.g. expired certificates, best practices)
• Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
• Reports with attack scenarios requiring MITM or physical access to victim's device
• Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
• Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
• Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
• Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
• Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
• CSV injection
• Malicious file upload (e.g. EICAR files, .EXE)
• HTTP Strict Transport Security Header (HSTS)
• Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
• Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
• Lack or bypass of rate-limiting, brute-forcing or captcha issues
• User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
• Weak password policies (e.g. length, complexity, reuse)
• Ability to spam users (email / SMS / direct messages flooding)
• Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
• Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
• Stolen non-valid secrets, credentials or information gathered from a third-party asset that we have no control over
• Exposed secrets, credentials or information on an asset under our control that are not applicable to the program’s scope
• Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes
• Pre-account takeover (e.g. account creation via oAuth)
• GraphQL Introspection is enabled
• Cache poisoning