Responsible Disclosure Policy

We are a global compliant company and take the security of our products and services very seriously. Despite stringent quality standards for the security of these systems, it may occur that there still is a vulnerability that slipped through the cracks of our quality assurance processes.

If you believe you have found a real or potential security vulnerability in any Airmeet-owned software or source code, then please report it to us as soon as possible at [email protected] We would like to work with you to protect our customers and our systems in a better way.

We will acknowledge receipt of your vulnerability report as soon as possible. In case your vulnerability report is a ‘valid issue’ then we will strive to send you regular updates about our progress.
If you are curious about the status of your disclosure please feel free to email us again at the above-mentioned e-mail address. If for some reason you do not receive a response within a reasonable time from us then please follow up via email to ensure we received your original message.

  1. Please always ensure to avoid any privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  2. Please only use exploits to the extent necessary to confirm the presence of any real or potential security vulnerability and do not use an exploit to compromise or exfiltrate data, establish persistent command-line access, or use the exploit to pivot to other systems.
  3. Please do not report any security vulnerabilities through public channels or to any third parties without our prior written consent, instead, please report them to the Airmeet Security Team at [email protected].
  4. We prefer all communications to be in English. Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
  • Type of issue (e.g. Remote Code Execution (RCE), Server-side request forgery (SSRF), SQL injection, cross-site scripting, etc.);
  • Full paths of (source) file(s) related to the manifestation of the issue;
  • When applicable, the location of the affected source code (tag/branch/commit or direct URL);
  • Any special configuration required to reproduce the issue;
  • Step-by-step instructions to reproduce the issue;
  • Impact of the issue, including how an attacker might exploit the issue this information will help us triage your report more quickly.

 

Please do not submit a high volume of low-quality reports on security vulnerabilities.

Please DO NOT disclose the vulnerability until we have been able to correct it. See below for possible publication.

  • Do not exploit the vulnerability by unnecessarily copying, deleting, adapting or viewing data. Or, for example, by downloading more data than is necessary to demonstrate the vulnerability.
  • Do not apply the following actions:
    • Placing malware (virus, worm, Trojan horse, etc.);
    • Copying, modifying, or deleting data in a system;
    • Making changes to the system;
    • Repeatedly accessing the system or sharing access with others;
    • Using automated scanning tools; (e.g. Nuclei, Zap, Burpscan Report, etc.)
    • Using the so-called “brute force” of access to systems;
    • Using denial-of-service or social engineering (phishing, vishing, spam, etc.).
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam, or third-party applications.
  • Immediately erase all obtained/exfiltrated data as soon as it is reported.
  • Do not perform actions that could have an impact on the proper functioning of the system, both in terms of availability and performance, but also in terms of confidentiality and integrity of the data.

 

Acts under this Responsible Disclosure Policy should be limited to conducting tests to identify potential vulnerabilities, and sharing this information with Airmeet. If, after the vulnerability has been removed, you may publish information about the vulnerability on social platform or in public or to any third party, only with our prior written approval by notifying us at least one month in advance. Hence, you can identify us in public or before any third party only after giving our explicit written approval.

Thank you

We would like to thank you for helping us in improving the security of our software. We really appreciate your efforts to disclose the issue responsibly and will make every effort to acknowledge your contributions.

If you have any questions, we encourage you to address them to the Airmeet Security Team at [email protected]. In case of doubt about the applicability of this Policy, please contact us first via the above-mentioned e-mail address, to ask for an explicit permission.

Airmeet reserves the right to change the content of this Policy from time to time or to terminate the Policy at any time.