Home > Exploit development > Leaking information with timing attacks on hashtables, part 1

Leaking information with timing attacks on hashtables, part 1

Timing attacks [1] are an important subclass of side channel attacks used to reveal cryptographic secrets, basing only on time needed by targeted devices or applications to perform specific computations.

It turns out these attacks can be applied in a more prosaic context — instead of encryption keys, they can help us leak pointers to objects on the heap or, if we are lucky, in .code/.data sections of targeted application. Leaking a pointer with fixed RVA reveals the imagebase, so ASLR becomes ineffective (ROP). Leaking a heap pointer makes expoitation of WRITE-ANYWHERE bugs easier, so in both cases it’s a win :).

This post provides a high-level description of a POC implementation of a timing attack on hashtable used in Firefox (tested on v4, v13, v14). POC is quite fast (takes few secs) and leaks a heap pointer to a JS object. A detailed explanation will be provided in a different post (part 2).

The trick


Consider a hash table using double hashing [2]. In this scheme, keys are hashed like so: h(k,j) = h_1(k)+jh_2(k) mod |T|, where h_1, h_2 are hash functions and |T| is the size of hash table. During insertion, j is incremented until a free slot is found, like shown below:

Lookups are performed the same way — j is incremented until key value in a slot matches, or the slot is empty.

It’s easy to see that the execution time of lookup(T,k) is proportional to the length of k‘s chain (number of collisions). In the above example CL(k)=2, since there were two collisions. The idea is to use this fact to learn the value of key being looked up. Firefox is nice enough to store pointers and user supplied integers in the same hashtable (not always, but in specific circumstances), so we can control the table’s layout completely. It worth noting that only the object’s pointer is used in hashing, so k=ptr (contents of strings are not taken into account).

Here’s how we are going to layout keys inside the table (using JS integers):

Yellow slots are taken, white are free. We have to leave some free space, since FF grows / shrinks tables dynamically, basing on the number of taken slots.

If we keep generating JS objects (with different pointers) and trying to look them up in T, we will finally find one that takes considerably longer than others to lookup. Let’s call this object Mstr (M – max., str – string, since we are using strings (atoms, to be more precise) in POC) and the lookup time of Mstr: LT(Mstr)=Mt.

Here’s an example of a long chain for Mstr (Firefox uses subtraction instead of addition while hashing):

In this example CL(Mstr)=5.

In order to find r=h_2(Mstr), we will use the observation that r divides h(k,i) - h(k, j) for any i,j<CL(k) (this isn’t always true, but I’ll omit the second case for brevity). Indeed, h(k,i)-h(k,j) = h_1(k)-ih_2(k) - h_1(k)+jh_2(k) = h_2(k)(j-i) = r(j-i). If we collect enough of chain’s elements, we can calculate their differences and take r=gcd(diffs). This equality holds with high probability — chance of failure decreases exponentially with the number of collected elements (the most significant term of the exact formula is (1/2)^n).

How to find elements on Mstr‘s chain? Remember that keys used to fill T are integers. We can remove a key and check if LT(Mstr) changed significantly. If it did, we know for shure that the removed key belongs to the chain.

Here’s an example:

We removed 4 and this caused CL(Mstr)=2, so the lookup time after removal (LTAR) is going to be lower than Mt/2. In order to deal with inaccuracies of the JS clock (Date object), we will accept only elements for which LTAR(Mstr)<Mt/2, so we are reducing our interest to the first half of the chain (red line on the diagram above). Without this restriction we would be unable to distinguish between keys that don’t belong to the chain and keys at the very end of it.

Obviously, removing keys one by one is too slow. Removing them in chunks in a bisect-like manner is better, but still has the running time proportional to |T|. It’s faster to use a randomized algorithm. Let’s say we chose random k elements to remove. Probability that we failed to hit any element of Mstr‘s chain is (1-CL(Mstr)/|T|)^k. The exponent is working in our favor, but we need to estimate CL(Mstr) somehow, so that we don’t waste too much time — (1/2)^{30} is as good as (1/2)^{100}, but the second requires greater k, so more elements to test.

We can estimate CL(Mstr) by collecting integers with increasingly long chains, and using their lookup times to create a linear regression model [3]. Model will provide a linear function g(x)=ax+b that interpolates collected data. Estimating CL(Mstr) is then a matter of evaluating CL(Mstr)=g(LT(Mstr)). Below is an example of collected data points and a linear function that fits them best. Y axis is time and X is the chain’s length.

Having CL(Mstr) we can pick k so that (1-CL(Mstr)/|T|)^k<\epsilon for any \epsilon>0. After we finally pick k, we chose k random keys and remove them. If LTAR(Mstr) dropped below Mt/2, it means that in the set we chose, there’s at least one key that belongs to the first part of the chain — we need to find it. In order to do so, we bisect the set of removed keys until only one is left. Running time: O(logk), if we disregard time necessary to add / remove keys from T.

After collecting enough (8 in POC) elements of chain, we compute r=gcd(...). The only thing left is to find h_1(Mstr) — the starting point.

Recall T‘s layout:

Consider how LT(Mstr) changes, when removing two keys: k_0 and k_0+r — we remove them separately and then measure LT(Mstr).

- if we remove 5 or 7, LT(Mstr) will not change, since 5, 7 do not belong to Mstr‘s chain,
- removing 4 or 6 will cause LT(Mstr)<Mt/2, since 4 and 6 are in the first half of chain,
- removing 8 will cause LT(Mstr)<Mt/2 and removing 10 will have no effect on LT(Mstr).

These 3 conditions are sufficient to recognize if we are inside, outside, or and the edge of chain.

Algorithm to detect the starting point is simple. Start from element for which LTAR(Mstr) is smallest (so it’s the closest element to starting point). With r we found earlier, do a binary search using the criteria above (inside, outside, hit) until hitting the edge (starting point).

With r=h_2(k) and start=h_1(k) it’s possible to recover k, which equals to ptr(Mstr).



This is a simplified description. There’s quite a lot of details that were omitted in this post for brevity, but are required for this trick to work.

I suspect (this type of) timing attacks will be useful for leaking information not only from browsers. The most likely candidates seem to be kernels and perhaps even remote servers. (EDIT: I mean this in ASLR context, not secret-password context).

Here’s the POC. Download all files and open lol.html (in Firefox ;)) to see how it works. POC was tested on xp, w7 and linux. Send me an email if it doesn’t work for you.

1. http://en.wikipedia.org/wiki/Timing_attack
2. http://en.wikipedia.org/wiki/Double_hashing
3. http://en.wikipedia.org/wiki/Linear_regression

About these ads
  1. 07/08/2012 at 15:26 | #1

    Timing attacks against hash tables on a remote server that is using java’s hashtables is possible. Build from Nate Lawson’s work on java string timing attacks, the hashtable is just an extension of that.

  2. p_k
    07/08/2012 at 15:34 | #2

    @Travis: link? Is the attack you mention about extracting passwords? I meant remotely leaking the imagebase, or weakening ASLR in any other way, so that it’s not necessary to use bruteforce in an exploit against, for example, apache.

    • 07/08/2012 at 15:41 | #3

      His work proves its possible to time a string compare in java. Hashtables dont directly use string compares, until a collision occurs. The good news with hashtables its easy to create collisions (http://www.ocert.org/advisories/ocert-2011-003.html)
      So once you have a collision the string compare timing attacks can begin (assuming its a table of strings)

      An example attack is storing an admin’s cookie value in a hashtable. Since we can detect when a collision occurs (on the lookup), we can figure out what location in the hashtable the admin cookie is; then send requests to start the string compare timing attack (Nate Lawson’s paper) Thats the scenario I was able to do an auth bypass in.

  3. p_k
    07/08/2012 at 16:02 | #4

    I see. The difference here is that the string’s address is used to compute the hash, not the contents. This complicates things and creates a different scenario. I think similarities to Nate’s work end after filling the hash table.

  4. 07/08/2012 at 16:10 | #5

    Sorry, Didn’t mean to hijack your post. I was just trying to build off your comment here: “I suspect (this type of) timing attacks will be useful for leaking information not only from browsers. The most likely candidates seem to be kernels and perhaps even remote servers.” Just wanted to point out that its for sure possible against remote servers in some contexts

  5. p_k
    07/08/2012 at 16:19 | #6

    Thanks for mentioning Nate’s work and the hashDOS thing. I should’ve mention these in the post.

  6. 08/08/2012 at 01:16 | #7

    AWESOME work. See also: “Through The Side Channel” from PyCon. Similar hash timing attacks for python. http://python.mirocommunity.org/video/4251/pycon-2011-through-the-side-ch

  7. p_k
    08/08/2012 at 07:50 | #8

    @s7ephen: thanks, cool video.

  8. 08/08/2012 at 21:46 | #9

    See also BH 2007 timing attack against the balanced b-tree data structure http://www.coresecurity.com/content/timing-attacks

  1. 14/08/2012 at 00:38 | #1

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

%d bloggers like this: