| Version | Supported |
|---|---|
| 0.1.x | ✅ |
The TerminAI team takes security vulnerabilities seriously. We appreciate your efforts to responsibly disclose your findings.
If you discover a security vulnerability, please DO NOT open a public issue. Instead, send an email to: marcus.hohlbein@example.com
Please include the following information in your report:
- Type of vulnerability (e.g., buffer overflow, injection, cross-site scripting, etc.)
- Location of vulnerability (where in the code the issue exists)
- Impact (what could happen if the vulnerability were exploited)
- Steps to reproduce (detailed steps to demonstrate the vulnerability)
- Proof of concept (if available, code or screenshots demonstrating the vulnerability)
- Initial Response: We will acknowledge receipt of your vulnerability report within 48 hours
- Detailed Assessment: We will provide a detailed response within 7 days, including:
- Confirmation of the vulnerability
- Severity assessment
- Timeline for patch release
- Coordination: We will work with you to understand and resolve the vulnerability
- Disclosure: We will aim to release a patch within 30 days of initial report
- Credit: With your permission, we will credit you in the security advisory
- Permission System: Always review bash commands before allowing execution
- Output Limits: Configure
MAX_OUTPUT_LINESto prevent excessive output - Environment Variables: Be careful with sensitive environment variables
- Network Access: Be aware that the CLI may make network requests for AI functionality
- Command Validation: Never execute commands without user permission
- Input Sanitization: Validate and sanitize all user inputs
- Error Handling: Don't expose sensitive information in error messages
- Dependencies: Keep dependencies updated and review security advisories
- Permission Prompts: Explicit user approval required before command execution
- Command Inspection: Users can review commands before execution
- Output Truncation: Configurable limits prevent terminal overflow
- Cancellation: Users can stop operations at any time
- Process Isolation: Commands are executed in separate processes
- Limited Scope: CLI operates within user's permissions and context
- No Privilege Escalation: CLI does not attempt to elevate privileges
- Command Injection: Prevented by explicit permission system
- Data Exposure: Mitigated through output limits and user controls
- Resource Exhaustion: Addressed with cancellation and limits
- Code Execution: Controlled through permission prompts
- Host System Security: Users are responsible for their system security
- AI Model Security: Security of upstream AI services is handled by providers
- Network Security: Users should ensure secure network environments
- Advisories: Security advisories will be published on GitHub
- Patch Notes: Security fixes will be documented in changelog
- Notifications: Updates will be announced through GitHub releases
- Security Lead: Marcus Hohlbein
- Email: marcus.hohlbein@example.com
- GitHub Issues: For non-sensitive security discussions
- Private Disclosure: For vulnerability reports
We thank security researchers and users who help us maintain the security of TerminAI. Your responsible disclosure helps keep our users safe.
Remember: Security is everyone's responsibility. If you see something, say something - privately and responsibly.