Skip to content

Security: cdin-editor/spec

Security

SECURITY.md

Security Policy

Scope

This repository contains design documents and a small reporting script (scripts/spec_report.py); it does not contain product implementation code. A security issue here means a design flaw in a contract (ABI, Frontend Protocol, extension contract) that would make a conforming implementation unsafe. Implementation bugs belong in the cdin repository's policy.

Reporting a Vulnerability

Please report security vulnerabilities to: bitsgenix@gmail.com

Please do not report security vulnerabilities through public GitHub issues.

You should receive a response within 48 hours. If for some reason you do not, please follow up to ensure we received your original message.

Please include the following information in your report:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • 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
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit it

Preferred Languages

We prefer all communications to be in English.

Policy

We follow the principle of Coordinated Vulnerability Disclosure.

There aren't any published security advisories