Description

Visma delivers software that simplifies and digitizes core business processes in the private and public sector. With presence across the entire Nordic region along with Benelux, Central and Eastern Europe, we are one of Europe’s leading software companies. We want to engage with responsible security researchers around the globe to further secure our services. No code is flawless and we believe that taking part in the Intigriti community can help us improve the security of our systems.

Bounties
Low
0.1 - 3.9
Medium
4.0 - 6.9
High
7.0 - 8.9
Critical
9.0 - 9.4
Exceptional
9.5 - 10.0
Tier 2
100
250
1,000
3,000
7,500
Tier 2
€100 - €7,500
Rules of engagement
Required
User-Agent: Intigriti-<username>- Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
max. 20 requests /sec
X-Bug-Bounty: Intigriti-<username>

In order to gain a positive relationship and avoid misinterpretation and vagueness, we would like you to review the following program rules before you report a vulnerability. By participating in this program, you agree to respect our policy.

Program Rules

  • Please do NOT publicly discuss or publish any vulnerability before it has been fixed and you have received explicit permission from us to do so. You can send us a video as proof of concept, but remember to change its privacy settings to private.
  • Perform testing only on in-scope assets and respect assets and activities which are out-of-scope. If unsure or need advice, contact us at security.testing@visma.com.
  • Only interact with accounts or devices you own or with explicit permission from the owner.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • If a vulnerability provides unintended access to data, limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept.
  • Cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information.
  • All publicly released 0 day exploits (or new published CVEs) have a blackout period of 5 business days before they will be accepted in this program.
  • Provide an appropriate level of detail with reproducible steps so that the issue can be easily reproduced.
  • Please include the HTTP requests/responses in the report. This will help us to search for duplicate reports using the endpoint and triage reports more effectively; include the vulnerable requests in the comment using markdown.
  • Please be aware that all reports for the same endpoint - regardless the HTTP verbs used (e.g. GET, POST, PUT, DELETE) will be considered duplicates as long as the fix is not applied.We will award, of course the original report. After the fix is applied, if we still get reports, these will be triaged accordingly.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Do not attempt to execute Denial of Service attacks.

Our promise to you

  • We will respond to your report as fast as we can and we aim for the following response targets:
    • Time to triage (from report submission): maximum 4 business days.
    • Time to bounty (from triage): maximum 4 business days.
    • Time to fix: 90 days.
  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We respect the safe harbour clause that you can find below.

Your promise to us

  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo, etc).

Legal

In connection with your participation in this program you agree to comply with all applicable local and national laws.
You may not participate in this program if you are currently employed or contracted by Visma.
You may not participate in this program if you are a resident or individual located within a country appearing on any U.S. or E.U. sanctions list.

Vulnerabilities obtained by exploiting Visma users or employees are not eligible for a bounty and will result in immediate disqualification from the program.

Visma has never given permission/authorization (either implied or explicit) to an individual or group of individuals to extract personal information or content of Visma's customers and publicize this information on the open, public-facing Internet without customer consent, nor has Visma ever given permission for programs or data belonging to Visma to be modified or corrupted in order to extract and publicly disclose data belonging to Visma.

Visma reserves the right to change this policy at any time. You can subscribe to program updates to be notified of any changes.

Domains
iOS

Visma Scanner
Visma Scanner is a mobile app used for sending receipts and invoices to your Visma accounting system.
The iOS version of the app can be found here:
https://apps.apple.com/us/app/visma-scanner/id564141518
Please read and follow the steps in the Startup guide to create an account and start hacking: https://vismabugbountyprod.z16.web.core.windows.net/VismaScanner-iMXxOpXkhOlTBUQtXfyA-getting-started.pdf

Out of scope:

  • Session invalidation issues (e.g. logout, password change, email change, role change, user deletion, etc)
  • Private screen exposure in the app
  • Stack traces from api calls
  • Jailbroken devices is out of scope
  • All options for login are out of scope, except eAccounting (please see details in the "Getting Started instructions document"

Connect
See instructions for domain "connect.identity.stagaws.visma.com".

Out of scope:

  • Session invalidation after enabling 2FA - by design intended to work like this

Visma Online
This is the old interface for the customer's administrators to administrate the company, where we still have some functionality that has not been moved to the new interface. For example invoicing information and everything regarding collaborations with AO. The collaboration part is out of scope as long as the use of student companies.
Please read the Getting Started Instructions in the "myservices.stage.vismaonline.com" asset description.

Out of scope:

  • Session invalidation issues (e.g. logout, password change, email change, role change, user deletion, etc).
  • The collaboration part is out of scope as long as the use of student companies. Collaboration is between Accounting Office and Client
Severity assessment

No impact means no bounty. We will always take into consideration the business impact and security impact when setting the final severity of the reports.
Monetary rewards will be offered for qualifying reports. The amount will vary depending on the severity. The "Bounties" section provides a general guideline for the amounts, but final rewards may be adjusted for actual business impact. For example an SQLi for a database containing no sensitive information may be rewarded a lower amount compared to an SQLi for a database with sensitive information.

We highly value good quality, actionable reports and that’s one of the the requirements for "Exceptional" severity category.

When duplicates occur, we will only accept the first report. A duplicate is a vulnerability that we are already aware of, regardless of how we first became aware of it (it could have also been discovered by us internally).

To get an idea of how we define severities, see the following table as a guideline:

Severity Vulnerability
Exceptional A quality report that shows exceptional impact to Visma and it's customers, typically otherwise in high or critical severity category
Critical Remote Code Execution (RCE)
Critical SQL Injection (SQLi)
Critical Authentication or Authorization Bypass
High Local File Inclusion
High Account Takeover
High Mass PII Extraction
High Horizontal Privilege Escalation across customer contexts
High Vertical Privilege Escalation
High XML External Entity Injection (XXE)
Medium Insecure Direct Object Reference (IDOR)
Medium Horizontal Privilege Escalation within the same customer context
Medium Server-Side Request Forgery (SSRF)
Medium Reflected Cross-Site Scripting
Medium Stored Cross-Site Scripting (XSS)
Medium DOM-based Cross-Site Scripting
Medium Cross-Site Request Forgery (CSRF)
Medium Sensitive Data Exposure
Medium Cross-Site Script Inclusion (XSSI)
Low GUID-based IDOR
Low Mass User Enumeration (without brute-forcing)
Low Clear text Submission of Passwords (over HTTP)
Low Open Redirect
Low HTML content injection
Low Broken Link Hijacking
Low PHP Info Disclosure
Low Rate limit issues on authentication endpoints
Informative Non-State Changing Cross-Site Request Forgery
Informative CSV/formula injection
Informative Server Information Page
Informative User Enumeration including WordPress Mass User Enumeration
Out of scope Text (non-html) content injection
Out of scope Non-Sensitive Data Disclosure
Out of scope Lack of, or weak, security headers
Out of scope Flash based CSRF
Out of scope DoS & DDoS
FAQ

Where can we get credentials for the app?

You can self-register on the application, but please don’t forget to use your @intigriti.me address. For more details, please read each asset description.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid Intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.