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 aim to validate all submissions within the below timelines (once your submission has been verified by Intigriti)

Working hours = Mo-Fr 9am - 5pm, except Swedish holidays

Check our fix
We offer up to €50 bonus to verify a resolved issue for us (when requested).
This remains at the discretion of Stravito to award.

Introduction

We are excited to introduce our Vulnerability Disclosure Program! At Stravito, we prioritize the protection of our products and services, striving to achieve a high level of security. However, we recognize that vulnerabilities may still exist. We kindly request that you do not exploit any discovered vulnerabilities but instead report them to us so we can take the necessary actions.

If you have identified a vulnerability in our websites or any of our systems, please report your findings to us promptly through this program. It is important to inform us of the vulnerability before disclosing it publicly, allowing us to address the issue as swiftly as possible.

We aim to collaborate with you to enhance the protection of our systems and promptly remediate any vulnerabilities. Please note that our Vulnerability Disclosure Program is not an invitation to actively scan our business network for weaknesses.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by Stravito.

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.

Accepted Issues and Severity
When reporting vulnerabilities, please consider attack scenario/exploitability and the security impact of the bug. We may choose not to accept or to modify the severity of submissions in cases where there is no clear exploit chain, these include:

• "Best Practice" configuration items not part of a functioning exploit chain.
• Header Issues such as X-Frame-Options, CSP, etc.
• Cookie Configuration such as Missing "Secure" Flag on non-sensitive cookies or missing HTTPOnly properties.
• Mail security configurations such as invalid, incomplete, or missing SPF/DKIM/DMARC records.
• SSL/TLS configurations.
• Non-Sensitive information disclosures such as software versions, banner identifications, descriptive error messages, descriptive headers (stack traces, application or server errors).
• Attacks requiring MITM or physical access to a device.
• Use of vulnerable libraries without an associated working PoC.

However, it is important to note that in some cases a vulnerability's priority will be modified due to its likelihood or impact. In any instance where a vulnerability rating is modified, an explanation will be provided to the researcher - along with the opportunity to make a case for a higher priority.

Please be aware, Stravito uses HubSpot for content management of our public website. We accept vulnerability reports for HubSpot components and configurations, however, in cases where the same component is determined to be vulnerable across multiple HubSpot pages / websites because of the shared codebase, these will be treated as one unique vulnerability with subsequent reports marked as duplicate.

How do I report vulnerabilities to Stravito?
Register an account at the Intigriti bug bounty hunting platform here and start reporting vulnerabilities, earning reputation points and possibly more!

Where can I get credentials for the applications?
We currently don’t offer any credentials to in scope of the vulnerability disclosure program.

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback using this form (note that this form will be checked periodically and should not be used for submission or support queries).