Security

Have you discovered a security flaw at KODE Labs? Please notify us before informing the outside world, so that we can first take action. Doing so is called ‘responsible disclosure’. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us. This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities. We encourage you to contact us to report potential vulnerabilities in our systems.

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly and KODE Labs will not recommend or pursue legal action related to your research. Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

• Tab-Nabbing
• Send malware
• Change the system
• Use ‘brute force’ to open the system
• Clickjacking on pages with no sensitive actions
• Do not submit a high volume of low-quality reports
• Repeatedly visit the system or share access with others
• Do not reveal the problem to others until it has been resolved
• Missing Security Headers without demonstrating a vulnerability
• Ability to send emails with no control over content without any limits
• Vulnerabilities only affecting users of outdated or unpatched browsers
• Open redirect – unless an additional security impact can be demonstrated
• Previously known vulnerable libraries without a working Proof of Concept
• Vulnerabilities that require physical access to users’ devices for exploitation
• Comma Separated Values (CSV) injection without demonstrating a vulnerability
• Full red-team penetration testing that involves unauthorized access to our servers
• Missing HttpOnly or Secure flags on cookies without demonstrating a vulnerability
• Missing best practices in SSL/TLS configuration without a working Proof of Concept
• Missing best practices in Content Security Policy without demonstrating a vulnerability
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Try denial of service or social engineering, physical security, spam or applications of third parties
• General low severity issues reported by automated scanners without a working Proof of Concept
• Software version disclosure / Banner identification issues / Descriptive error messages or headers
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Copy, change, or delete data in the ICT system concerned (as an alternative, you can create a directory listing of the system)
• 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
• Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to “pivot” to other systems

Notify us as soon as possible after you discover a real or potential security issue.

• E-mail your findings to [email protected]
• 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.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Be in English, if possible

This policy applies to the following systems and services:*.kodelabs.com

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their Disclosure Policy (if any). If you aren’t sure whether a system is in scope or not, contact us at [email protected] before starting your research.

Although we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document.

If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

• Within 3 business days, we will acknowledge that your report has been received.
• To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
• KODE Labs does not provide payment to reporters for submitting vulnerabilities yet.
• Reporters submitting vulnerabilities to KODE Labs, in so doing, waive any claims to compensation.
• Part of vulnerability rewards are (Letter of recognition) which it depends on the impact of an issue.