repository·main·Indexed 26 days ago
https://github.com/projectdiscovery/interactshAn open-source tool for detecting out-of-band (OOB) interactions to identify vulnerabilities triggering external network requests (DNS, HTTP, SMTP, etc.). It includes a client library, a server for gathering interactions, and a CLI client. The documentation covers installation via Go or Docker, deployment using Ansible playbooks, self-hosting server configuration, and integrations with Burp Suite, OWASP ZAP, and Caido.
You can point the client to a self-hosted server using the -server flag. This flag accepts a single server or multiple servers separated by commas.
To connect to a protected self-hosted server, use the -token flag alongside the -server flag.
Interactsh can be integrated into OWASP ZAP via the OAST add-on.
Options > OAST > General and set it as the default.Interactsh can wrap Responder in a Docker container to expose various service ports. Interactions are retrieved by monitoring the shared log file Responder-Session.log in the temp folder.
Setup Steps:
interactsh:docker build . -t interactsh-responder flag:sudo interactsh-server -responder -d localhostDefault Ports:
docker build . -t interactshBefore deploying the application using the provided Ansible playbooks, ensure the following tools and dependencies are installed on your local machine:
sudo apt install ansible-corebrew install ansiblesudo -H pip install -Iv 'resolvelib<0.6.0'ansible-galaxy collection install community.dockerA ready-to-run Docker image is available for the interactsh-client.
docker run projectdiscovery/interactsh-client:latestUse the quickssrf extension to use Interactsh within the Caido Proxy.
The deploy.yaml playbook automates the deployment of the interactsh application to a remote server. It performs the following actions:
Steps to deploy:
deploy.yaml and update the parameters in the vars section to match your environment requirements.ansible-playbook deploy.yaml.--extra-vars to specify a specific container tag.If the default service ports are already in use, you can run interactsh-server on custom ports and use a reverse proxy like Nginx to forward traffic to the standard ports (80, 443, 25, 53, etc.).
Use the http/stream proxy directive (proxy_pass) in Nginx to handle HTTP/HTTPS and TCP/UDP services (like SMTP and DNS).
# http/https
http {
server {
listen 443 ssl;
server_name mysite.com;
ssl_certificate /etc/nginx/interactsh.pem;
ssl_certificate_key /etc/nginx/interactsh.key;
location / {
proxy_pass https://interachsh.mysite.com:80/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
}
stream {
# smtp
server {
listen 25;
proxy_pass interachsh.mysite.com:8025;
}
# dns
server {
listen 53;
proxy_pass interachsh.mysite.com:8053;
}
server {
listen 53 udp;
proxy_pass interachsh.mysite.com:8053;
}
}To use protected Interactsh servers, you need a PDCP_API_KEY (available at https://cloud.projectdiscovery.io). You can configure it in two ways:
-auth flag.-auth flag followed by your key.To collect node metrics and logs for your project, you can deploy a Grafana agent using the grafana_agent.yaml playbook.
Steps to configure and deploy:
grafana_agent.yaml and update the variables according to your project requirements.export GRAFANA_CLOUD=****
export PROM_URL=****
export PROM_PASS==****
export PROM_USERNAME==****
ansible-playbook grafana_agent.yamlinteractsh client library to programmatically retrieve external interactions for a generated URL (e.g., by making an HTTP request to the URL and checking for callbacks).You can use Interactsh within Burp Suite using either the original or the revised extension.
Original Extension:
Revised Extension: