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)
• LVM Versicherung reserves the right to change the terms of this program without giving any reason and/or notification to you. Please check for any updates before submitting a new finding.

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
The following SLAs are in business days (Mon-Fri) and may exclude days where there are regional holidays in Germany (NRW).

This remains at the discretion of LVM to award.

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!

Domains in scope

Every publicly accessible domain belonging to our group is part of this program and in particular, IT-assets belonging to the lvm.de domain.

Our worst-case scenarios are:

• Publishing false information or content that is harmful to our business on our website.
• Obtaining sensitive user data.
• Command execution on production services.

Known Issues (Date last updated: 06/02/2025 - DD/MM/YYYY)

• Potential Risk for BREACH Attacks due to enabled http compression
• Potential Risk due to disabled OCSP Stapling
• TCP Timestamps information disclosure
• ICMP Timestamp reply information disclosure (CVE-1999-0524)
• SSL server certificate not pinned in any apps

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

General

• Since we use various automatic scanners for vulnerability management and gain those results as part of regular business, we cannot accept any submissions found by using automatic scanners.
• 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
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty

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

We currently don’t offer any credentials to test user roles.

Pathway to our private Bug Bounty Program
We value meaningful collaboration with the community. By submitting high-quality reports to our Vulnerability Disclosure Program, you may be invited to join our private Bug Bounty Program that offers: paid bounties for verified vulnerabilities, closer collaboration with our security team.