Number 1 Rule: No interaction with real users or listings on the platform

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)

Eligibility & Disclosure Policy

• Let us know as soon as possible upon discovery of a potential security issue, and we’ll make every effort to quickly resolve the issue.
• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• While we encourage you to discover and report to us any vulnerabilities you find in a responsible manner, the following conduct is strictly prohibited:
• Performing actions that may negatively affect Autoscout24 or its users (e.g. Spam, Brute Force, Denial of Service…).
• Accessing, or attempting to access, data or information that does not belong to you.
• Destroying or corrupting, or attempting to destroy or corrupt, data or information that does not belong to you.
• Conducting any kind of physical or electronic attack on Autoscout24 personnel, property or data centers.

Program Rules

• Any testing that involves financial transactions must be approved by us prior to any testing being done.
• 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.
• Only interact with accounts you own
• Results from automated scans are not permitted (nmap, sqlmap, IBM AppScan etc. )
• Test only with your own team(s) when investigating bugs, and do not interact with other accounts without the consent of their owners.
• Access or expose only customer data that is your own.
• Any testing that involves financial transactions must be approved by us prior to any testing being done.
• Mass creation of test/fake listings is not permitted
• Mass creation of leads/sending out inquiry mails to any listings is not permitted
• No interaction with real users on the platform (this includes but is not limited to sending leads to real listings, receiving/processing leads from real users, creating a rating for a real dealer)

Bounties

AutoScout24 may pay bounties for vulnerabilities submitted via this program. The decision about that and bounty amount remains solely within discretion of AutoScout24.

Assets of AutoScout24

Please note! Most reports we receive have little or no security impact or are already known. To avoid a disappointing experience when reporting us, please take a moment and consider if the issue you want to report actually has a realistic attack scenario.

This is a VDP. We appreciate any submissions as part of responsible disclosure.

Testing as dealer is out of scope of this VDP
Interacting with real persons and listing on our platform is out of scope of this VDP

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

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

Mobile

• Shared links leaked through the system clipboard
• 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

This program follows Intigriti's triage standards

Where can we get credentials for the app?

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

Where can we get credentials for testing as dealer?

Testing as dealer is out of scope of this VDP.