| Version | Supported |
|---|---|
| 0.x.x | ✅ |
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via email to: alexandre@vanoix.com
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 1 week
- Resolution: Depends on severity
- Critical: Within 1 week
- High: Within 2 weeks
- Medium: Within 1 month
- Low: Next release
- We follow coordinated disclosure
- Credit will be given in release notes (unless you prefer anonymity)
- We may request a CVE for critical vulnerabilities
ztick is a time-based job scheduler that executes shell commands via configured rules. This combination introduces specific security risks:
- Arbitrary Code Execution: ztick executes shell commands defined in rules using the system shell. It runs with the same permissions as the user executing the binary.
- TCP Protocol Exposure: ztick listens on a TCP port (
127.0.0.1:5678by default). Ensure the listen address is not exposed to untrusted networks without TLS enabled. - TLS Configuration: When using TLS, ztick enforces TLS 1.3 via system OpenSSL. Ensure certificates are kept up to date and private keys are properly protected.
- Persistence Files: The append-only logfile contains all scheduled jobs and rules. Protect logfile access with appropriate file permissions.
- Configuration Files: Config files may contain file paths and network addresses. Treat them as sensitive and do not commit secrets.
- Bind locally: Keep the default
127.0.0.1listen address unless TLS is configured. - Enable TLS: Use
tls_certandtls_keyconfiguration for any non-loopback deployment. - Least Privilege: Run ztick with the minimum necessary permissions. Avoid running as root.
- File Permissions: Restrict read/write access to logfile and config files.
- Keep Updated: Keep ztick and its dependencies updated to the latest version.
Subscribe to security advisories:
- Watch this repository (Releases only)
- Check GitHub Security Advisories