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 https://aws.amazon.com/security/penetration-testing/
• 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.

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:

• Fluid Flow, 15 minutes video
• Structural Analysis, 15 minutes video
• Natural Convection, 35 minutes video

Highlighted

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.

• https://www.simscale.com/api/v1/projects/*
• www.simscale.com/forum/users/*.json
• 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.

The chat because it's hosted by Intercom.

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 and Geolocation Lookup 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

Out of scope domains

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

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 @intigriti.me address.

Where can we get credentials for the API?

API keys can be managed in the API keys page.