Musts and Must Nots

General

• Any automatized scan must be throttled reasonably (recommended 5 req/sec, with burst up to 20 req/sec for 10 seconds)
• For HTTP requests using a clearly identifiable User-Agent or custom Header is required and mandatory. For anything else (non-HTTP) submitting the IP address that was used for testing is required and mandatory. Ignoring these may result in your submission being rejected and not awarded!

Attacks in this list are explicitly forbidden and may be object to legal consequences

• Social engineering or other attacks on our employees
• Explicit DoS and DDoS attacks (performance-type) are forbidden
• Attacks which go beyond confirming the vulnerability:
  • Attempt on exfiltrating customer data (instead, use your own accounts for such tests)
  • Attempt on pivoting or privilege escalation in case you gained some access to our systems. You probably have already achieved the highest bounty

Forbidden only on Production environments

• Attacks which cannot be safely executed, without permanently harming our infrastructure or data, or could cause considerable amount of downtime (SQL injection with unsafe commands, path traversal with overwrite, persistent DoS, etc.)

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 validate all submissions within the below timelines, once your submission has been verified by Intigriti.

Reward
Our Bug Bounty program is currently private and closed. You may submit your findings in our VDP (Vulnerability Disclosure Program), which will be triaged the same way, but we cannot guarantee any rewards. If the finding is within scope and severe enough, we may decide to reward and invite you to our closed program.

Introduction

We invite you to explore our Vulnerability Disclosure Program and contribute to the ongoing security of Kaufland Marketplace. If you’re a security researcher with a passion for ethical hacking, your expertise can make a real difference in safeguarding our platform and our customers. Let's work together to create a safer digital marketplace for all. Note that if your finding is within scope and severe enough, we may decide to reward and invite you to our private program.

Our worst-case scenarios are:

Data exfiltration - Any vulnerability that allows attackers to access, exfiltrate, or expose sensitive information such as Personally Identifiable Information (PII) related to customers and sellers. This includes unauthorized access to data storage, APIs, or any data processing pipelines.

Payment process - Vulnerabilities that enable attackers to manipulate payment processes, such as altering the price of items, bypassing payment gateways, or creating fraudulent transactions. This includes any flaws in the checkout process, payment integrations, or order management systems.

Injection attacks - Vulnerabilities that allow attackers to perform injection attacks, such as SQL injection, command injection, or file upload attacks, which can lead to unauthorized access to databases, backend systems, or operating systems. This includes any injection vulnerabilities in web applications, APIs, or backend services.

Remote code execution - Any vulnerability that allows an attacker to execute arbitrary code on your servers or within your infrastructure. This includes vulnerabilities in software, misconfigured services, or insecure scripting that can be exploited remotely.

Cloud misconfiguration - Misconfigurations in cloud services or infrastructure that can lead to unauthorized access, data leaks, or compromise of cloud resources. This includes issues like publicly accessible storage buckets, insecure API endpoints, or misconfigured access controls.

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.

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program

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
• Missing or insecure CSP
• Insufficient anti-bot and scraping protection

General

• 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

This program follows Intigriti's triage standards

Where can we get credentials for the app?

For the webshop (https://kaufland.de) you can self-register on the application, but please don’t forget to use your @intigriti.me address, as described here.
For all the other sites, these are currently black-box and no credentials are offered.