Skip to content

[NOT UP-TO-DATE] Build a database of libc offsets to simplify exploitation

Notifications You must be signed in to change notification settings

ajabep/libc-database

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

71 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Changelog

⚠️ This fork do not aim to be updated or better than the origin, it aims to be a code base to pull requests only.

This fork aims to fix various biases of the origin (some points are inspired by a review of forks).

(very soon)

  • MERGED Various small fixes
  • MERGED Fix Ubuntu watching
  • MERGED Fix Debian watching
  • MERGED Add other distro
  • MERGED Add other libc than glibc (musl, dietlibc, etc.)
  • MERGED Be able to search a libc using a BuildID/MD5/SHA1/SHA256/etc.

(A day if possible)

  • Add db compression
    Requirements

    • The goal of the compression is to reduce the size of db, but it has not to make it unusable (the search and other usages have to stay fast). The compression can be slower: it already takes lots of time and can be run as a cron or in background.
    • The compression must be optional, and have to be easily disabled.
    • Tools have to works both with compressed files and uncompressed ones.
    • It's better if the tool used to compress is a standard tool, present on lots of distros, by default.

    Benchmarks (absolutely not perfect, but "it works")

    • Benchmarks have been done using the database build with all libs and distro (branch otherLibs). This database is composed of 685 libraries and is 1,3 GB.
    • .info and .url files are too small to need compression.
    • Using zstd compression using a custom dictionary to compress .so and .symbols (using the highest compression level), we gain 64% (db size: 447MB). A single-file compression can be parallelized.
    • Using zstd compression without using a custom dictionary to compress .so and .symbols (using the highest compression level), we gain 64% (db size: 449MB). A single-file compression can be parallelized.
    • Using xz compression to compress .so and .symbols (using the highest compression level), we gain 67% (db size: 409MB). A single-file compression can be parallelized.
    • Using bzip2 compression to compress .so and .symbols (using the highest compression level), we gain 60% (db size: 494MB).
    • Using gzip compression to compress .so and .symbols (using the highest compression level), we gain 59% (db size: 551MB).

    Design
    In order to be configurable (enable or not compression, the tools to use and compression options), we use environment variables. By default, the compression is enabled, using xz and its highest compression level (-9e). It will only compress .so files: .symbols files are already used in clear text. It's faster to have a gain like that.

  • Reduce time of computation of some tools (I thinking about search: we can extract hash when adding files)

  • MERGED Review symbols, to see if other symbols can be accurate

  • Improve the dump executable

  • See if adding ld library is relevant, and do it if it is

  • Add libc dbg symbols if relevant

Building a libc offset database

Fetch all the configured libc versions and extract the symbol offsets. It will not download anything twice, so you can also use it to update your database:

$ ./get

You can also add a custom libc to your database.

$ ./add /usr/lib/libc-2.21.so

Find all the libc's in the database that have the given names at the given addresses. Only the last 12 bits are checked, because randomization usually works on page size level.

$ ./find printf 260 puts f30
archive-glibc (id libc6_2.19-10ubuntu2_i386)

Find a libc from the leaked return address into __libc_start_main.

$ ./find __libc_start_main_ret a83
ubuntu-trusty-i386-libc6 (id libc6_2.19-0ubuntu6.6_i386)
archive-eglibc (id libc6_2.19-0ubuntu6_i386)
ubuntu-utopic-i386-libc6 (id libc6_2.19-10ubuntu2.3_i386)
archive-glibc (id libc6_2.19-10ubuntu2_i386)
archive-glibc (id libc6_2.19-15ubuntu2_i386)

Dump some useful offsets, given a libc ID. You can also provide your own names to dump.

$ ./dump libc6_2.19-0ubuntu6.6_i386
offset___libc_start_main_ret = 0x19a83
offset_system = 0x00040190
offset_dup2 = 0x000db590
offset_recv = 0x000ed2d0
offset_str_bin_sh = 0x160a24

Check whether a library is already in the database.

$ ./identify /usr/lib/libc.so.6
id local-f706181f06104ef6c7008c066290ea47aa4a82c5

Or find a libc using a hash (currently BuildID, MD5, SHA1 and SHA256 is implemented)

$ ./identify bid=ebeabf5f7039f53748e996fc976b4da2d486a626
id libc6_2.17-93ubuntu4_i386
$ ./identify md5=af7c40da33c685d67cdb166bd6ab7ac0
id libc6_2.17-93ubuntu4_i386
$ ./identify sha1=9054f5cb7969056b6816b1e2572f2506370940c4
id libc6_2.17-93ubuntu4_i386
$ ./identify sha256=8dc102c06c50512d1e5142ce93a6faf4ec8b6f5d9e33d2e1b45311aef683d9b2
id libc6_2.17-93ubuntu4_i386

Download the whole libs corresponding to a libc ID.

$ ./download libc6_2.23-0ubuntu10_amd64
Getting libc6_2.23-0ubuntu10_amd64
    -> Location: http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc6_2.23-0ubuntu10_amd64.deb
    -> Downloading package
    -> Extracting package
    -> Package saved to libs/libc6_2.23-0ubuntu10_amd64
$ ls libs/libc6_2.23-0ubuntu10_amd64
ld-2.23.so ... libc.so.6 ... libpthread.so.0 ...

About

[NOT UP-TO-DATE] Build a database of libc offsets to simplify exploitation

Topics

Resources

Stars

Watchers

Forks

Languages

  • Shell 100.0%