By participating in this program, you agree to:

• Respect the Community Code of Conduct
  • Please pay particular attention to this part:
    "Do not execute intrusive commands within production environments
    Invasive queries and commands should be limited to the absolute minimum necessary to prove their impact. For example, using simple tests such as a "hello world" message, checking the database version, or retrieving the database name. Commands such as phpinfo(), which may reveal sensitive data, variables, or keys, are discouraged and only allowed when absolutely required. Additionally, no write operations or data manipulation should be performed without explicit permission from the platform administrators. Participants must prioritize the integrity, security, and privacy of all systems and data."
• Respect the Intigriti Terms and Conditions
  • Please pay particular attention to this part:
    "14.3. You must use all reasonable endeavors to prevent and mitigate potential damages to Companies, Intigriti or any third party, and in particular to Assets and other computer systems and/or data. Without being restrictive, this implies that you must take precautions to ensure that no data is altered, lost or corrupted and to avoid service interruption, hardware or software damage or system failure."
• 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.

This remains at the discretion of Axel Springer National Media & Tech GmbH & Co. KG to award.

Check our fix
We offer up to €50 bonus to verify a resolved issue for us (when requested).
This remains at the discretion of Axel Springer National Media & Tech GmbH & Co. KG 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!

Domain in Scope
In addition to the domains listed above, all subdomains of our our main domains are in scope!

Our worst-case scenarios are:

• Publishing fake news on our website.
• Obtaining sensitive user data.
• Command and execution on production services.

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 including the attached full in scope domain list, is out of scope for this program.

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
• 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
• 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.