Skip to content

Security: terraboops/chattermax

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.1.x

Reporting a Vulnerability

We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.

How to Report

Do NOT open a public GitHub issue for security vulnerabilities.

Instead, please email us at: me@terratauri.com

Include the following information:

  • Description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact
  • Any suggested fixes (optional)

What to Expect

I'll respond as quickly as I can. For critical issues, expect a fix within days. I'll coordinate disclosure timing with you.

Scope

The following are in scope for security reports:

  • Authentication bypass
  • Authorization flaws
  • Remote code execution
  • SQL injection
  • XML/XXE vulnerabilities
  • Denial of service (protocol-level)
  • Information disclosure

Out of Scope

  • Denial of service via resource exhaustion (expected behavior for MVP)
  • Issues in dependencies (report to upstream)
  • Social engineering attacks

Security Best Practices

When deploying Chattermax:

  1. Use a reverse proxy with TLS (nginx, Caddy) until native TLS is implemented
  2. Run as non-root user with minimal privileges
  3. Firewall - Only expose necessary ports
  4. Keep updated - Apply security patches promptly
  5. Strong passwords - Enforce strong user passwords

Acknowledgments

We appreciate responsible disclosure and will acknowledge security researchers who help improve Chattermax security.

There aren’t any published security advisories