Scope

Paradime Labs, Inc’s Responsible Disclosure Policy covers the following products:

• Paradime Labs, Inc’s core platform

We intend to increase our scope as we build capacity and experience with this process. Researchers who submit a vulnerability report to us will be given full credit on our website once the submission has been accepted and validated by our product security team.

Legal Posture

Paradime Labs, Inc will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting inbox. We openly accept reports for the currently listed Paradime Labs, Inc products. We agree not to pursue legal action against individuals who:

• Engage in testing of systems/research without harming Paradime Labs, Inc or its customers.

• Engage in vulnerability testing within the scope of our vulnerability disclosure program.

• Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testingagainst their devices/software, etc.

• Adhere to the laws of their location and the location of Paradime Labs, Inc. For example, violating laws that would only result in a claim by Paradime Labs, Inc (and not a criminal claim) may be acceptable as Paradime Labs, Inc is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.

• Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.

How to Submit a Vulnerability

To submit a vulnerability report to Paradime Labs, Inc’s Product Security Team, please utilize the following email security@paradime.io.

Preference, Prioritization, and Acceptance Criteria

We will use the following criteria to prioritize and triage submissions.

Ineligible Vulnerabilities:

Below are some examples of issues that are out of scope from eligible vulnerabilities:

• Account squatting by preventing users from registering with certain email addresses

• Attacks requiring MITM or physical access to a user's device

• Best practice reports without a valid exploit (e.g., use of "weak" TLS ciphers)

• Clickjacking on pages with no sensitive actions

• Comma Separated Values (CSV) injection without demonstrating a vulnerability

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Denial of service

• Disclosure of server or software version numbers

• Hypothetical subdomain takeovers without supporting evidence

• Issues that are premised on unlikely user interaction

• Missing best practices in Content Security Policy

• Missing best practices in SSL/TLS configuration

• Missing email best practices (invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Missing HttpOnly or Secure flags on cookies

• Open redirect - unless an additional security impact can be demonstrated

• Perceived security weaknesses without concrete evidence of the ability to compromise a user (e.g., missing rate limits, missing headers, etc.)

• Previously known vulnerable libraries without a working Proof-of-Concept

• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis

• Rate limiting or bruteforce issues on non-authentication endpoints

• Reports exploiting the behavior of, or vulnerabilities in, outdated browsers

• Reports of spam

• Self-XSS

• Session invalidation or other improved-security related to account management when a credential is already known (e.g., password reset link does not immediately expire, adding MFA does not expire other sessions, etc.)

• Social engineering

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)

• Tabnabbing

• Unconfirmed reports from automated vulnerability scanners

• User/merchant enumeration

• Vulnerabilities only affecting users of outdated or unpatched browsers (less than 2 stable versions behind the latest released stable version)

What we would like to see from you:

• Well-written reports in English will have a higher probability of resolution.

• Reports that include proof-of-concept code equip us to better triage.

• Reports that include only crash dumps or other automated tool output may receive lower priority.

• Reports that include products not on the initial scope list may receive lower priority.

• Please include how you found the bug, the impact, and any potential remediation.

• Please include any plans or intentions for public disclosure.

What you can expect from Paradime Labs, Inc:

• A timely response to your email (within 5 business days).

• After triage, we will send an expected timeline, and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.

• An open dialog to discuss issues.

• Notification when the vulnerability analysis has completed each stage of our review.

• Credit after the vulnerability has been validated and fixed.

If we are unable to resolve communication issues or other problems, Paradime Labs, Inc may bring in a neutral third party to assist in determining how best to handle the vulnerability.