Skip to content

Security: Real-Fruit-Snacks/Slipstream

Security

SECURITY.md

Security Policy

Supported Versions

Only the latest release of Slipstream is supported with security updates.

Version Supported
latest
< latest

Reporting a Vulnerability

Do NOT open public issues for security vulnerabilities.

If you discover a security vulnerability in Slipstream, please report it responsibly:

  1. Preferred: Use GitHub Security Advisories to create a private report.
  2. Alternative: Email the maintainers directly with details of the vulnerability.

What to Include

  • Description of the vulnerability
  • Steps to reproduce
  • Affected versions
  • Potential impact
  • Suggested fix (if any)

Response Timeline

  • Acknowledgment: Within 48 hours of receipt
  • Assessment: Within 7 days
  • Fix & Disclosure: Within 90 days (coordinated responsible disclosure)

We follow a 90-day responsible disclosure timeline. If a fix is not released within 90 days, the reporter may disclose the vulnerability publicly.

What is NOT a Vulnerability

Slipstream is a penetration testing tool designed for authorized security assessments. The following behaviors are features, not bugs:

  • SSH session interception and command routing
  • Tunnel management via SSH control sockets
  • File transfer via SFTP/SCP/cat/base64 fallback chain
  • Passive filesystem mapping from command output
  • Per-command session logging and capture
  • Target identification by SSH host key fingerprint
  • Automatic OS detection from SSH output
  • Credential and loot file collection via !loot

These capabilities exist by design for legitimate security testing. Reports that simply describe Slipstream working as intended will be closed.

Responsible Use

Slipstream is intended for authorized penetration testing, security research, and educational purposes only. Users are responsible for ensuring they have proper authorization before using this tool against any systems.

There aren’t any published security advisories