SimScale enables engineering teams to access accurate and fast simulation, on their terms, without compromises. We make engineering simulation technically and economically accessible from everywhere, at any time, and at any scale, in the cloud. We deliver instant access to fluid, thermal, and structural simulation to over 300,000 users. With SimScale, engineering simulation has moved from a complex and cost-prohibitive desktop application to an inclusive, agile, cloud-native simulation platform.

Tier 2
€200 - €6,000
Rules of engagement
Not applicable
max. 2 requests/sec
Not applicable

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)

Infrastructure notes

  • We are hosting at AWS, so please take into account their penetration testing policy which you can find at
  • We integrate 3rd-party closed-source software. Please be aware that we won't be able to fix all bugs internally but depend on other vendors.
  • We provide compute resources, storage, and data transfer to our users. Please avoid excessive consumption of those resources.
  • Please avoid creation of too many public projects and forum posts, or delete them after testing.

Our promise to you:

  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We will respond to reports within 2-3 days.

SimScale API

Tier 2


The API doc is available at

In order to access the SimScale API an API key is required which can be requested from the Intigriti support ("Ask scope question"). Please note that only a limited number of API keys will be issued at a time.

SimScale Platform

Tier 2

The following areas and paths under domain

User registration and login

Paths: /signup/*, /signin/*, /onboarding/*

Dashboard with project pages and user profile

Paths: /dashboard, /projects/*, /users/*
Examples (login required):

Workbench including CAD mode and Post-Processor

Paths: /workbench/*
Examples (login required):

Public project library

Paths: /projects/*

Related API endpoints

All API endpoints used by UIs listed above.
Paths: /api/*, /csm/*, /postprocessing/*

In scope

We are happy to announce our first bug bounty program! We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed!

Focus areas

Beside the classic web application vulnerabilities (XSS, SQLi, RCE, etc.), we are especially interested in vulnerabilities that affect our customer's trust into our platform, such as:

  • Access to private customer data (e.g. projects, CAD files, simulation results)
  • Privilege escalation (both vertical and horizontal)
  • Account takeover

Getting started

The SimScale platform is a complex application and contains a lot of functionality.

To get an impression of the functionality of the workbench we recommend to walk through one or more tutorials which are also available as video:


During the signup/onboarding process please select the "Community" account and avoid requesting the "Professional Trial". Failure to do so may result in a bounty reward being revoked.

Out of scope

Domain and the remaining paths not listed under SimScale Platform.


  • Landing page
  • Documentation
  • Blog
  • Forum


The creation date, last modification date etc of users, public projects and other things which are meant to be public, are not considered to be sensitive. If information is not mentioned in the web application, it is not sensitive by default. Any information disclosure that does not contain PII or other information that cannot directly be used to cause harm to the company or its users, on endpoints mentioned below will be closed as out of scope.

  • Other endpoints that disclose similar information as the above

If the endpoint does contain PII of a user, please make sure that it is not mentioned anywhere on the website.


  • 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 on pages with no sensitive actions
  • Host header injection without proven business impact
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username / email enumeration
  • E-mail bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing / Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file


  • 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, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • 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

Out of scope domains

  • Any domain that is not listed in the Domains section, is out of scope for this program
Severity assessment

This program follows Intigriti's contextual CVSS standard.


Where can we get credentials for the app?

You can self-register on the application but please don’t forget to use your address
During the signup/onboarding process please select the "Community" plan and avoid requesting the "Professional Trial".

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.

last contributors
Overall stats
submissions received
average payout
accepted submissions
total payouts
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
+3 weeks
avg. time to triage
< 2 days
closed a submission
closed a submission
created a submission
created a submission
closed a submission
created a submission
closed a submission
created a submission
closed a submission
closed a submission