We release patches for security vulnerabilities in the following versions:

We take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to:

security@redasgard.com

When reporting a security vulnerability, please include:

1. Description: A clear description of the vulnerability
2. Steps to Reproduce: Detailed steps to reproduce the issue
3. Impact: Description of the potential impact
4. Environment: OS, Rust version, plugin configuration, and any other relevant details
5. Proof of Concept: If possible, include a minimal code example that demonstrates the issue

• Acknowledgment: We will acknowledge receipt of your report within 48 hours
• Initial Assessment: We will provide an initial assessment within 5 business days
• Regular Updates: We will keep you informed of our progress
• Resolution: We will work with you to resolve the issue and coordinate disclosure

• Initial Response: Within 48 hours
• Status Update: Within 5 business days
• Resolution: Within 30 days (depending on complexity)

When reporting vulnerabilities, please consider:

1. Plugin Security: Malicious plugin execution
2. Capability Escalation: Unauthorized capability access
3. Sandbox Bypass: Bypass of plugin sandboxing
4. Code Injection: Malicious code injection through plugins
5. Performance: DoS through resource exhaustion
6. Memory Safety: Unsafe memory operations or buffer overflows

Common attack vectors to test:

• Malicious Plugins: Plugins with malicious code
• Capability Escalation: Unauthorized access to capabilities
• Sandbox Bypass: Bypass of plugin isolation
• Code Injection: Injection of malicious code
• Resource Exhaustion: DoS through resource consumption
• Privilege Escalation: Unauthorized privilege escalation
• Data Exfiltration: Unauthorized data access

1. Validate Plugins: Only load trusted plugins
2. Implement Sandboxing: Use proper plugin isolation
3. Capability Controls: Implement proper capability controls
4. Keep the library updated to the latest version
5. Monitor for security advisories
6. Implement proper access controls

1. Test with malicious plugins regularly
2. Implement defense in depth
3. Use the library correctly according to documentation
4. Consider additional validation for critical applications
5. Monitor security updates
6. Implement proper plugin validation

• Plugin Validation: Built-in plugin validation
• Capability Controls: Capability-based security
• Sandboxing: Plugin isolation mechanisms
• Memory Safety: Rust's memory safety guarantees
• Type Safety: Compile-time type safety
• Configurable Security: Adjustable security settings

• Plugin Signing: Implement plugin code signing
• Sandboxing: Use additional sandboxing mechanisms
• Capability Controls: Implement strict capability controls
• Access Controls: Implement proper access controls
• Logging: Log security events for monitoring
• Regular Updates: Keep dependencies and the library updated

1. Assessment: We assess the severity and impact
2. Fix Development: We develop a fix in private
3. Testing: We thoroughly test the fix
4. Release: We release the fix with a security advisory
5. Disclosure: We coordinate disclosure with reporters

Security advisories are published on:

• GitHub Security Advisories: https://github.com/redasgard/module-registry/security/advisories
• Crates.io: Security notices in release notes
• Email: Subscribers to security@redasgard.com

We follow responsible disclosure practices:

1. Private Reporting: Report vulnerabilities privately first
2. Coordinated Disclosure: We coordinate disclosure timing
3. Credit: We give credit to security researchers
4. No Legal Action: We won't take legal action against good faith research

• Test Responsibly: Don't test on production systems
• Respect Privacy: Don't access or modify data
• Report Promptly: Report findings as soon as possible
• Follow Guidelines: Follow this security policy

In Scope:

• Plugin security vulnerabilities
• Capability escalation attacks
• Sandbox bypass techniques
• Code injection attacks
• Memory safety issues
• Performance DoS attacks

Out of Scope:

• Social engineering attacks
• Physical security issues
• Issues in dependencies (report to their maintainers)
• Issues in applications using this library
• Issues in plugins themselves

For security-related questions or to report vulnerabilities:

• Email: security@redasgard.com
• PGP Key: Available upon request
• Response Time: Within 48 hours

We thank the security researchers who help keep our software secure. Security researchers who follow responsible disclosure practices will be acknowledged in our security advisories.

By reporting a security vulnerability, you agree to:

1. Not disclose the vulnerability publicly until we've had a chance to address it
2. Not access or modify data that doesn't belong to you
3. Not disrupt our services or systems
4. Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services

Thank you for helping keep Module Registry and our users safe! 🔌🛡️