lattera to speak at Thotcon 0x9

My Thotcon presentation has been accepted! Below is the presentation abstract:

Without exploit mitigations and with an insecure-by-default design, writing malware for FreeBSD is a fun task, taking us back to 1999-era Linux exploit authorship.

Several members of FreeBSD's development team have claimed that Capsicum, a capabilities/sandboxing framework, prevents exploitation of applications. Our in-depth analysis of the topics below will show that in order to be effective, applying Capsicum to existing complex codebases lends itself to wrapper-style sandboxing. Wrapper-style sandbox is a technique whereby privileged operations get wrapped and passed to a segregated process, which performs the operation on behalf of the capsicumized process. With a new libhijack payload, we will demonstrate that wrapper-style sandboxing requires ASLR and CFI for effectiveness. FreeBSD supports neither ASLR nor CFI.

Tying into the wrapper-style Capsicum defeat, we'll talk about advances being made with libhijack, a tool announced at Thotcon 0x4. The payload developed in the Capsicum discussion will be used with libhijack, thus making it easy to extend.

We will also learn the Mandatory Access Control (MAC) framework in FreeBSD. The MAC framework places hooks into several key places in the kernel. We'll learn how to abuse the MAC framework for writing efficient rootkits.

Attendees of this presentation should walk away with the knowledge to skillfully and artfully write offensive code targeting both the FreeBSD userland and the kernel.

This presentation dives in depth regarding:
1) defeating wrapper-style Capsicum sandboxing with ret2sandbox_open (re-usable template exploit provided)
2) easy runtime process infection on amd64 and arm64
3) abusing the MAC framework to write rootkits (rootkit code will be released)

libhijack in PoC||GTFO 0x17!

It is with pride and pleasure that SoldierX's libhijack was featured in PoC||GTFO 0x17. Shawn Webb, the author of both libhijack and the article, spent months writing the article and going through a private peer review process.

The unedited version is posted below. The full issue can be found here (warning: large polyglot PDF). I hope you enjoy the article.

Hijacking Your Free Beasties

In the land of red devils known as Beasties exists a system devoid of
meaningful exploit mitigations. As we explore this vast land of
opportunity, we will meet our ELFish friends, [p]tracing their very
moves in order to hijack them. Since unprivileged process debugging is
enabled by default on FreeBSD, we can abuse PTrace to create anonymous
memory mappings, inject code into them, and overwrite PLT/GOT entries.
We will revive a tool called libhijack to make our nefarious
activities of hijacking ELFs via PTrace relatively easy.

Nothing presented here is technically new. However, this type of work
has not been documented in this much detail, tying it all into one
cohesive work. In Phrack 56, Silvio Cesare taught us ELF research
enthusiasts how to hook the PLT/GOT. The Phrack 59 article on Runtime
Process Infection briefly introduces the concept of injecting shared
objects by injecting shellcode via PTrace that calls dlopen(). No
other piece of research, however, has discovered the joys of forcing
the application to create anonymous memory mappings in which to inject

This is only part one of a series of planned articles that will follow
libhijack's development. The end goal is to be able to anonymously
inject shared objects. The libhijack project is maintained by the
SoldierX community.

Welcome Back to Jerbo and Site Cleanup

It's been awhile since we've posted a news update. I'm not going to lie, 2017 has been a busy year for most of us and a slow year for SX. I'm happy to announce that Jerbo has returned from his hiatus and is taking up the reigns on OFACE. Expect an updated release on that soon. We're also examining the site and our private tools collection to see where we should clean things up and what things we might be willing to share with the public. Expect 2018 to be much better, as near the end of it (October to be exact) - will be 20 years old. Quite a long time for a hacking group and honestly I'm surprised we've been around so long. After all of the arrests in the late 1990s and early 2000s, I honestly didn't know how much more we could take.

While you wait for various updates, please visit us in our IRC and get to know the community. We also welcome any suggestions on how we can do things better as I know much of the site is pretty dated at this point.

64 Hijacked ARMs

As discussed in A Hijack Revival, libhijack is under active development again. Today, I'm announcing version 0.8.0, which breaks both API and ABI from 0.7.0. The breakage is worth it, though. With version 0.8.0, libhijack now works on arm64. This marks a milestone achievement in libhijack: the first port to a non-x86 architecture.

It's interesting to note that during development, a local kernel DoS for arm64 was found, reported upstream, and subsequently fixed..

Download the source from GitHub here.

Here's the highlights of libhijack 0.8.0:

  • New architecture supported: arm64
  • Add ERROR_NOTSUPPORTED error code
  • Make the memory mapping code architecture-dependent
  • Add API for getting/setting various registers in an architecture-agnostic fashion
  • Add API for querying instruction alignment
  • Detect the base address better
  • Switching from ptrace(PT_READ_D) to ptrace(PT_IO) for reading data
  • Add sample exit(55) shellcode for arm64
  • Add various sanity checks and clean up a bit of code

Next item to knock off the TODO list: anonymous injection of shared objects.                                 |   1 +                                    |  17 +++++++---
 hijack/Makefile                              |   6 ++--
 hijack/hijack.c                              |  18 +++++++++--
 include/hijack.h                             |  24 +++++++-------
 libhijack/Makefile                           |  13 +++++---
 libhijack/arch/aarch64/hijack_machdep.h      |  37 ++++++++++++++++++++++
 libhijack/arch/aarch64/inst.c                |  46 +++++++++++++++++++++++++++

A Hijack Revival

Over a decade ago, while standing naked and vulnerable in the comfort of my steaming hot shower, I gathered my thoughts as humans typically attempt to do in the wee hours of the morning. Thoughts of a post-exploitation exercise raced in my mind, the same thoughts that made sleeping the night before difficult. If only I could inject into Apache some code that would allow me to hook into its parsing engine without requiring persistance. Putting a file-backed entry into /proc/pid/maps would tip off the security team to a compromise.

The end-goal was to be able to send Apache a special string and have Apache perform a unique action based on the special string.

FelineMenace's Binary Protection Schemes whitepaper provided inspiration. Silvio Cesare paved the way into PLT/GOT redirection attacks. Various Phrack articles selflessly contributed to the direction I was to head.

Alas, in the aforementioned shower, an epiphany struck me. I jumped as an awkward stereotypical geek does: like an elaborate Elaine Benes dance rehearsal in the air. If I used PTrace, ELF, and the PLT/GOT to my advantage, I could cause the victim application to allocate anonymous memory mappings arbitrarily. In the newly-created memory mapping, I could inject arbitrary code. Since a typical operating system treats debuggers as God-like applications, the memory mapping could be mapped without write access, but as read and execute only. Thus enabling the stealth that I sought.

The project took a few years to develop in my spare time. I ended up creating several iterations, taking a rough draft/Proof-of-Concept style code and rewriting it to be more efficient and effective.

I had toyed with FreeBSD off-and-on for over a decade by this point, but by-and-large I was still mostly using Linux. FreeBSD gained DTrace and ZFS support, winning me over from the Linux camp. I ported libhijack to FreeBSD, giving it support for both Linux and FreeBSD simultaneously.

RoboAmp 1.0.3 Released

Due to some changes to google voice, RoboAmp 1.0.2 stopped working. RoboAmp has been updated to adapt to these changes, as well as a few other minor changes. You can get the new version here. If you would like to see more changes to RoboAmp or any of our other SX Labs releases, please drop by our IRC.

Syndicate content