sickcodes / security

Collection of CVEs from Sick Codes, or collaborations on https://sick.codes security research & advisories.
https://sick.codes/category/security/
85 stars 18 forks source link
advisories bugs cve cwe mitre security vulnerabilities

Sick Codes Security Advisories

- View All Advisories

- Submit a Vulnerability

- Public PGP Key

- VDP (see below, or external)

SICK CODES Vulnerability Disclosure Program & Vulnerability Disclosure Policy

Terms Generated Under CC0-1.0 License using the Disclose.io project terms generator.

Introduction

SICK CODES welcomes feedback from security researchers and the general public to help improve global security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any software, hardware, or device, or in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by SICK CODES, as well as certain digital assets that are particularly interesting or urgent in nature.

Out of Scope

Vulnerabilities that are already covered by another CNA mya be reported to us, which we will in turn forward to the respective CNA as found on https://cve.mitre.org/cve/request_id.html.

Our Commitments

When working with us, according to this policy, you can expect us to:

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

Official Channels

Please use any of those channels, or email, to report security issues, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

We will do our very best to protect you, and if you wish to remain anonymous during disclosure, you are more than welcome to make that request.