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)

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.

Introduction

We are pleased to launch Storebrand’s Vulnerability Disclosure Program. While we continuously work to improve the security of our systems, we recognize that vulnerabilities can still occur. We welcome responsible, good-faith security research and appreciate your help in identifying issues we may have missed.

This section outlines which assets are in scope, what types of findings are most valuable to us, and any relevant technical context to support your research.

In-Scope Assets

The following assets are currently in scope:

• Customer-facing web applications and digital services owned and operated by Storebrand
• Publicly accessible APIs owned and operated by Storebrand
• Mobile applications published and maintained by Storebrand
• Internet-facing systems and services that are part of Storebrand’s production environment

Only assets owned and operated by Storebrand are in scope unless explicitly stated otherwise. If you are unsure whether a specific asset or system is in scope, please use the feedback form to confirm before testing.

Useful Infrastructure Information

• Production systems are monitored and logged
• Testing must be performed in a non-disruptive manner
• Automated scanning should be limited and respectful
• Please avoid actions that could impact service availability or customer data

If you are unsure whether a specific test is permitted, please contact us before proceeding.

Feedback

If you would like to help us improve this program or share feedback, please submit anonymous feedback here:

Program feedback link

Please note this form will be checked periodically and should not be used for submission or support queries.

Important OOS reminder

• Only assets owned and operated by Storebrand are in scope unless explicitly stated otherwise. If you are unsure whether a specific asset or system is in scope, please use the feedback form to confirm before testing.
• Third-party services or platforms not owned or operated by Storebrand
• Physical security
• Social engineering (phishing, vishing, smishing)
• Denial-of-Service (DoS / DDoS) attacks
• Issues requiring access to stolen credentials

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 impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Content injection without being able to modify the HTML
• 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 based on the proof of concept.

Where can we get credentials?

We currently don’t offer any credentials.