By participating in this program, you agree to:

• Respect the Community Code of Conduct (link to https://go.intigriti.com/coc)
• Respect the Terms and Conditions (link to https://go.intigriti.com/tac)
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Eligibility to Participate
To be eligible to participate in our program, you have to:

• Be at least 18 years of age if you test using a Sixt Account or register for an account.
• Not be employed by Sixt or any of its affiliates or an immediate family member of a person employed by Sixt or any of its affiliates.
• Not be a resident of, or make submissions from, a country against which Germany has issued export sanctions or other trade restrictions.
• Not be in violation of any national, state, or local law or regulation with respect to any activities directly or indirectly related to the Vulnerability Disclosure Program.
• Not be using duplicate Intigriti accounts.
  If
  (i) you do not meet the eligibility requirements above
  (ii) you breach any of these Program Terms or any other agreements you have with Sixt SE or its affiliates
  (iii) we determine that your participation in the Intigriti Program could adversely impact us, our affiliates or any of our users, employees or agents, then we may remove you from the Intigriti Program and disqualify you from receiving any benefit of the relevant Intigriti Programs.

Special Sixt rewards:

• Car rental voucher or other Sixt specific rewards will only be available in specific countries and to researchers over 18 years of age. The countries where car rental voucher are applicable: Germany, Switzerland, Austria, Italy, Spain, Netherlands, Belgium, Luxemburg, France, UK, US

We are happy to announce our VDP on Intigriti!
We will also start a Private program in the near future and you will have the chance to be invited to that. To be eligible for an invite, you need to find a valid medium or higher vulnerability an in scope asset.

We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed!
We are specifically looking for:

• leaking of personal data.
• horizontal / vertical privilege escalation.
• SQLi.
• modification of content on the corporate website.
• access to management systems hosted on *.sixt.com or servers that hosts corporate resources.

Important notes

1. Shared codebase disclaimer
Our websites share the same codebase across countries so they can contain common issues. If a specific issue has already been found in another country website it will be treated as a duplicate. Focus on the country domains listed In Scope.

2. Quality requirements
Please make sure your report follows our quality standards as mentioned in the FAQ section
In case reports are not written according to the standards, they may not be eligible for a Swag or Reward.

3. Remember: Quality over Quantity

Swag and Rewards

All researchers who submit a valid Medium or higher submission, will also receive an invitation to the private BB program which we'll be launching soon!

We are giving vouchers to the Intigriti swag store as rewards. Please find an overview per severity below!

• Medium: 25€ swag voucher or cash of 25€
• High: 50€ swag voucher or cash of 50€
• Critical: Car rental voucher for a week-end OR 100€ swag voucher or cash 100€
• Exceptional: Car rental voucher for a week OR 150€ swag voucher or cash 150€

See Rules of engagament for the conditions under which a car rental voucher is possible

log4j Bonus

We are adding the log4j vulnerability into our scope. We will be awarding a 1k bonus on these vulnerabilities.
We’re curious to see what you’ll find!

If you have additional questions about our program feel free to contact us through Intigriti's support.
Lastly, if you believe a vulnerability has impact, we want to know about it! Remember to provide a clear impact indication.

Highlighted

• Open Redirects
• HTTP Response Splitting (HRS)

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program
• Domains in the list below are OUT OF SCOPE:
• https://sixt-leasing
• https://siemens.smc.sixt.com/
• https://s004-px01.s004.smc.sixt.com/
• https://s004-px02.s004.smc.sixt.com/
• https://p001-slweb-px.p001.slweb.smc.sixt.com
• s003-lb-siemens-stage.s003.smc.sixt.com
• s002-lb-siemens-test.s002.smc.sixt.com
• s004-lb-siemens.s004.smc.sixt.com
• app.rental-images.sixt.com
• b2cleasing.typo3.sixt.de
• corporate.typo3.sixt.de
• domainparking.sixt.com
• fleetcheck.sixt.com
• intranet.sixt.com
• lacb2c.typo3.sixt.de
• lkw.sixt.com
• lkw.sixt.de
• logistics.sixt.com
• partner.sixt.de
• partner.typo3.sixt.de
• promo.sixt.com
• promo.typo3.sixt.de
• reporting.sixt.de
• rproxy-firenze1.sixt.de
• rproxy-firenze2.sixt.de
• sixtbook.sixt.com
• webservices.sixt.com
• drying-little-tears.org
• 185.97.224.12
• 185.97.224.13

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that cannot be used to exploit other users
• Dom-XSS that cannot 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 are not 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
• In case that the same vulnerability is reported on more than one environment (DEV, STAGING, PROD), 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
• Video only proof-of-concepts (PoCs) will not be considered.
• Send push notifications/SMS messages/emails without the ability to change content
• Entering a Sixt Station or Offices and high-jacking an unattended terminal or hardware

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
• Attacks requiring installing malicious applications onto the victim's device

This program follows Intigriti's contextual CVSS standard

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.

Can I submit more than one vulnerability in the same report?

No, please submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.

What information should I provide on a report?

Please add general data like: used URL/APP, timestamp, user account.
Describe the use case you intended to process and describe the steps as detailed as possible in order for the triage team to reproduce your findings.
Think through the attack scenario and exploitability of the vulnerability and provide as many clear details as possible for our team to reproduce the issue (include screenshots if possible).
Include your understanding of the security impact of the issue, the more detail you can provide, the better.
To ease our research, provide timestamps of the activitiy, in order for us to easier find the corresponding actions in our logging.

Remember: A vulnerability must be verifiable and reproducible for us to be considered in-scope.

During my research, I paid for a reservation at Sixt, can it be reimbursed?

No, we cannot reimburse researchers for paynow (pre-paid) reservations and real journeys with our products, even though it might be part of your research activity. Please bear this in mind.

I have a personal account at Sixt, can I use it?

No, please do not use this for your vulnerability research. Use of intigriti email is MANDATORY.