Report a vulnerability

If you believe you’ve discovered a security issue that meets Marad’s definition of a vulnerability, please report it to our security team using one of the methods below. We do not respond to bulk submissions generated by automated scanners. If you’ve used such a tool, we recommend having a security professional validate the findings before submitting a report. Our vulnerability reporting policy applies to our web application Marad and its portal.

Procedure

• E-mail your findings to [email protected]
• Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data
• Do not reveal the problem to others until it has been resolved,
• Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and
• Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.

What we promise

• We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,
• If you have followed the instructions above, we will not take any legal action against you in regard to the report,
• We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
• We will keep you informed of the progress towards resolving the problem,
• In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise)
• As a token of our gratitude for your assistance, we may offer a reward for security issues with a high impact. The amount of the reward will be determined based on the system* (for example our servers, application, etc.), severity of the leak, and the quality of the report.

Definition of a vulnerability

• Marad defines a security vulnerability as a weakness in our products or infrastructure that could be exploited to compromise the confidentiality, integrity, or availability of our systems or data.
• The following types of findings are not considered security vulnerabilities:
  • The presence or absence of HTTP headers such as X-Frame-Options, Content-Security-Policy, or X-Content-Type-Options. These are best practices, but their absence alone does not constitute a vulnerability.
  • Missing security-related attributes on non-sensitive cookies. While we apply appropriate security settings to sensitive cookies, non-sensitive cookies may not include attributes like HttpOnly or Secure, and this is not treated as a vulnerability.
  • Exposed stack traces. Stack traces alone are not considered a security issue. However, if a stack trace includes personally identifiable information or user-generated content, please submit a detailed report.
  • Auto-complete being enabled or disabled in forms or input fields.