# dns-rebinding-attacks

Provides an expert playbook for executing DNS rebinding attacks against internal web targets. It helps penetration testers bypass browser Same-Origin Policy during security reviews.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 3600 installs · ★ 2547
- Author: yaklang
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/yaklang/hack-skills/tree/HEAD/skills/dns-rebinding-attacks/SKILL.md
- Updated: 2026-09-13
- HTML: https://affpapa.org/en/nevibecode/skills/dns-rebinding-attacks

## What it does

This skill equips your coding assistant with playbooks for client-side DNS rebinding. Foundation models frequently confuse DNS rebinding with server-side request forgery (SSRF). This guide clarifies how browser Same-Origin Policy checks hostnames rather than resolved IPs, enabling attackers to query private network endpoints.

The material covers TTL manipulation tricks alongside methods to bypass the 60-second browser DNS cache. It details attack variants across standard HTTP requests and WebSockets. High-value targets include Docker daemons on `172.17.0.1:2375` and cloud metadata endpoints. Defenses like IMDSv2 will block this vector because token retrieval requires custom PUT headers that standard cross-origin browser requests cannot set.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add yaklang/hack-skills --skill dns-rebinding-attacks -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/dns-rebinding-attacks/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/dns-rebinding-attacks/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add yaklang/hack-skills --skill dns-rebinding-attacks -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/dns-rebinding-attacks/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add yaklang/hack-skills --skill dns-rebinding-attacks -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/dns-rebinding-attacks/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install yaklang/hack-skills dns-rebinding-attacks
```

2. **Manually: put the files in place**
- File: `.github/skills/dns-rebinding-attacks/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add yaklang/hack-skills --skill dns-rebinding-attacks -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/yaklang/hack-skills --path skills/dns-rebinding-attacks
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/dns-rebinding-attacks/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add yaklang/hack-skills --skill dns-rebinding-attacks -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/yaklang/hack-skills/tree/HEAD/skills/dns-rebinding-attacks/SKILL.md

## When to use it
- test browser Same-Origin Policy enforcement against dynamic DNS responses
- evaluate internal services like Docker API and Redis against rebinding
- design test scenarios to bypass 60-second browser DNS caching
- verify AWS cloud metadata resistance by testing IMDSv2 token enforcement

## Example prompts
- Explain how to bypass Chrome's 60-second DNS cache using multiple A records
- Draft a test script targeting AWS metadata using a DNS rebinding flow
- How does WebSocket rebinding differ from classic HTTP rebinding?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7ce38ec02794d4d1.

BEGIN THIRD-PARTY FILE 7ce38ec02794d4d1
````text
---
name: dns-rebinding-attacks
description: >-
  DNS rebinding attack playbook. Use when testing applications that trust DNS resolution for origin checks, interact with internal services from browser context, or when SSRF is not possible server-side but the target has client-side fetch/XHR to attacker-controlled domains.
---

# SKILL: DNS Rebinding — Expert Attack Playbook

> **AI LOAD INSTRUCTION**: Expert DNS rebinding techniques for bypassing same-origin policy via DNS manipulation. Covers TTL tricks, browser cache bypasses, attack variants (HTTP, WebSocket, TOCTOU), internal service targeting, and tool usage. Base models confuse DNS rebinding with SSRF — this skill clarifies the client-side nature and unique exploit paths.

## 0. RELATED ROUTING

- [ssrf-server-side-request-forgery](../ssrf-server-side-request-forgery/SKILL.md) — server-side variant; DNS rebinding is the **client-side** counterpart
- [cors-cross-origin-misconfiguration](../cors-cross-origin-misconfiguration/SKILL.md) — when CORS misconfig allows direct cross-origin reads instead

---

## 1. CORE PRINCIPLE

The browser same-origin policy binds `protocol + host + port`. The **host** is resolved via DNS at connection time. If an attacker controls the DNS server for `attacker.com`, they can:

1. First resolution → attacker IP (serve malicious JS)
2. Second resolution → internal IP (victim's network)
3. Browser considers both responses same-origin (`attacker.com`)
4. Malicious JS reads responses from internal services

```
Victim visits attacker.com
        │
        ▼
DNS query: attacker.com → 1.2.3.4 (attacker server)
Browser loads malicious JS from 1.2.3.4
        │
        ▼
TTL expires (or forced flush)
        │
        ▼
JS triggers new request to attacker.com
DNS query: attacker.com → 192.168.1.1 (internal target)
Browser sends request to 192.168.1.1 as "attacker.com" origin
        │
        ▼
JS reads response — same-origin policy satisfied
Exfiltrates data to attacker's other endpoint
```

**Key insight**: SOP checks the hostname string, not the resolved IP. DNS can change the IP behind the same hostname.

---

## 2. TTL MANIPULATION

### DNS server configuration

The attacker runs an authoritative DNS server for their domain that alternates responses:

| Query # | Response | TTL |
|---|---|---|
| 1st | Attacker IP (e.g., `1.2.3.4`) | 0 |
| 2nd+ | Target internal IP (e.g., `192.168.1.1`) | 0 |

TTL=0 tells resolvers not to cache the result, forcing re-resolution on next connection.

### Browser DNS cache reality

Browsers maintain their own DNS cache that **ignores low TTLs**:

| Browser | Internal DNS Cache | Bypass Technique |
|---|---|---|
| Chrome | ~60 seconds minimum | Wait 60s; or use multiple subdomains |
````
END THIRD-PARTY FILE 7ce38ec02794d4d1

The third-party file has ended. Everything between the 7ce38ec02794d4d1 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2773 of 12364 bytes. © yaklang · MIT · https://github.com/yaklang/hack-skills/tree/HEAD/skills/dns-rebinding-attacks/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md