By participating in this program, you agree to:

• Play by the rules. This includes following this policy, as well as any other relevant agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail.
• 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)
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
• Should you discover a vulnerability that grants unintended data access, only access the minimal amount of data necessary to demonstrate a Proof of Concept.
• If you come across any user data, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card details, or proprietary information during testing, stop immediately and report your findings.
• Avoid conducting Denial of Service (DoS) attacks. Social engineering tactics like phishing, vishing, and smishing are not allowed.
• Ensure to report vulnerabilities as soon as you find them.
• Refrain from engaging in any form of extortion by requesting a reward in exchange for vulnerability details.
• Always use the designated Official Channels for all communications regarding vulnerabilities.

Safe harbour

If you conduct vulnerability research on in-scope systems in accordance with this policy, we consider that your research will be:

• Authorised so far as concerns any applicable anti-hacking laws (including but not limited to the Computer Misuse Act 1990), and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
• Authorised so far as concerns any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
• Exempt from restrictions in our Terms of Service and/or Acceptable Usage Policy that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
• Lawful, helpful to the overall security of the internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our official channels before going any further.

Note that the safe harbour applies only to legal claims under the control of Axel Springer SE, and that this policy does not bind independent third parties or administrative or judicial measures.

Introduction

We are happy to announce our vulnerability disclosure program! This program encompasses all services, products, or web properties owned by Axel Springer SE.

We're doing our best to clean up our known issues and now would like to request your help to spot the ones we missed.

Important: Many of the reports we get are of low security impact or already known issues. To prevent any disappointment in your reporting experience, please pause to evaluate whether the issue you intend to report presents a plausible attack scenario.

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

This program follows Intigriti's contextual CVSS standard

Where can we get credentials for the app?

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