smartworldarafath/rea_skill

payloads-dns-rebinding

DNS rebinding changes the IP address of an attacker controlled machine name to the IP address of a target application, bypassing the and thus allowing the browser to make arbitrary requests to the target application and read their responses.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/smartworldarafath/rea_skill --skill payloads-dns-rebinding

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

DNS Rebinding Payloads

Source: PayloadsAllTheThings/DNS Rebinding Category: payloads-research | Skill ID: payloads-dns-rebinding

Overview

DNS rebinding attack payloads for bypassing SOP and accessing internal services via browsers.

This skill integrates the full PayloadsAllTheThings (PATT) payload library for the DNS Rebinding Payloads domain into the REA_Skill framework. Use it during authorized penetration testing, bug bounty research, security audits, and CTF challenges.

Workflow

1. Recon & Identification

  • Identify the target technology stack and injection points
  • Enumerate endpoints, parameters, and input vectors
  • Determine applicable payload categories from the reference below

2. Payload Selection

  • Browse the PATT payload library for the attack class
  • Select encoding-appropriate payloads for the target environment
  • Consider WAF bypass variants and obfuscation techniques

3. Exploitation (Authorized Only)

  • Test payloads in order: passive → active → escalation
  • Document every payload tested and its response
  • Capture PoC evidence (screenshots, HTTP logs, curl output)

4. Verification & Reporting

  • Confirm the vulnerability with a clean minimal PoC
  • Map findings to CVE/CWE where applicable
  • Report with remediation recommendations and code fixes

Full PATT Reference

DNS Rebinding

DNS rebinding changes the IP address of an attacker controlled machine name to the IP address of a target application, bypassing the same-origin policy and thus allowing the browser to make arbitrary requests to the target application and read their responses.

Summary

Tools

Methodology

Setup Phase:

  • Register a malicious domain (e.g., malicious.com).
  • Configure a custom DNS server capable of resolving malicious.com to different IP addresses.

Initial Victim Interaction:

  • Create a webpage on malicious.com containing malicious JavaScript or another exploit mechanism.
  • Entice the victim to visit the malicious webpage (e.g., via phishing, social engineering, or advertisements).

Initial DNS Resolution:

  • When the victim's browser accesses malicious.com, it queries the attacker's DNS server for the IP address.
  • The DNS server resolves malicious.com to an initial, legitimate-looking IP address (e.g., 203.0.113.1).

Rebinding to Internal IP:

  • After the browser's initial request, the attacker's DNS server updates the resolution for malicious.com to a private or internal IP address (e.g., 192.168.1.1, corresponding to the victim’s router or other internal devices).

This is often achieved by setting a very short TTL (time-to-live) for the initial DNS response, forcing the browser to re-resolve the domain.

Same-Origin Exploitation:

The browser treats subsequent responses as coming from the same origin (malicious.com).

Malicious JavaScript running in the victim's browser can now make requests to internal IP addresses or local services (e.g., 192.168.1.1 or 127.0.0.1), bypassing same-origin policy restrictions.

Example:

  1. Register a domain.
  2. Setup Singularity of Origin.
  3. Edit the autoattack HTML page for your needs.
  4. Browse to http://rebinder.your.domain:8080/autoattack.html.
  5. Wait for the attack to finish (it can take few seconds/minutes).

Protection Bypasses

Most DNS protections are implemented in the form of blocking DNS responses containing unwanted IP addresses at the perimeter, when DNS responses enter the internal network. The most common form of protection is to block private IP addresses as defined in RFC 1918 (i.e. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). Some tools allow to additionally block localhost (127.0.0.0/8), local (internal) networks, or 0.0.0.0/0 network ranges.

In the case where DNS protection are enabled (generally disabled by default), NCC Group has documented multiple DNS protection bypasses that can be used.

0.0.0.0

We can use the IP address 0.0.0.0 to access the localhost (127.0.0.1) to bypass filters blocking DNS responses containing 127.0.0.1 or 127.0.0.0/8.

CNAME

We can use DNS CNAME records to bypass a DNS protection solution that blocks all internal IP addresses. Since our response will only return a CNAME of an internal server, the rule filtering internal IP addresses will not be applied. Then, the local, internal DNS server will resolve the CNAME.

bash
$ dig cname.example.com +noall +answer
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> example.com +noall +answer
;; global options: +cmd
cname.example.com.            381     IN      CNAME   target.local.

localhost

We can use "localhost" as a DNS CNAME record to bypass filters blocking DNS responses containing 127.0.0.1.

bash
$ dig www.example.com +noall +answer
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> example.com +noall +answer
;; global options: +cmd
localhost.example.com.            381     IN      CNAME   localhost.

References


REA MCP Integration

javascript
// REA MCP — Automated payload injection via REA tools
// Use analyze_function, procedure_pseudo_code, or observe_native_calls
// to identify injection sinks, then apply payloads from this skill.

Legal Notice

⚠️ Authorized Use Only. All payloads in this skill are for security research, penetration testing with written permission, CTF competitions, and defensive study. Unauthorized use against systems you do not own or have explicit permission to test is illegal.
같은 저장소의 Skills

더 많은 Skills

모든 Skills
smartworldarafath
커뮤니티

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일
smartworldarafath
커뮤니티

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

1시간 설치 수
2
GitHub Stars
5
업데이트
11월 8일