views:

977

answers:

4

Given two different messages, A and B (maybe 20-80 characters of text, if size matters at all), what is the probability that the MD5 digest of A is the same as the MD5 digest of B and the SHA1 digest of A is the same as the SHA1 digest of B? That is:

(MD5(A) == MD5(B)) && (SHA1(A) == SHA1(B))

Assume no malicious intent, i.e., that the messages are not selected with an aim of finding a clash. I just want to know the odds of this happening naturally.

I'm thinking the chances are "astronomically low," but I'm not sure how to verify this.

More information: the size of the pool of possible messages is restricted, but large (several hundred million). Birthday paradox situations are exactly what I'm worried about.

+28  A: 

Assuming uniform spread in the range of MD5 and SHA-1 hashes for random strings (which isn't the case), and assuming we're only talking about two strings and not talking about a pool of strings (so we avoid birthday-paradox-type complexities):

An MD5 hash is 128 bits wide, and SHA-1's is 160. With the above assumptions, two strings A and B have a probability of colliding P if both hashes collide. So

P(both collide) = P(MD5 collides) * P(SHA-1 collides)

And

P(MD5 collides) = 1/(2^128)
P(SHA-1 collides) = 1/(2^160)

So

P(both) = 2^-128 * 2^-160 = 2^-288 ~= 2.01 x 10^-87

Again, if you have a pool of strings and you're trying to determine the probabilities of collisions with the pool, you're in the domain of the birthday paradox and this probability I've calculated here doesn't apply. That and hashes aren't as uniform as they should be. In reality you're going to have a much higher collision rate, but it will still be tiny.


EDIT

Since you are dealing with a birthday paradox situation, apply the same logic as the solution to the birthday paradox. Let's look at it from the point of view of just one hash function:

N := the number of hashes in your pool (several hundred million)
S := the size of your hash space (2^288)
Therefore,
P(There are no collisions) = (S!)/(S^N * (S - N)!)

Let's pretend we have a nice even number of hashes like 2^29 (roughly 530 million).

P = (2^288!)/(2^288^(2^29) * (2^288 - 2^29)!)

In short, I don't even want to think about calculating this number. I'm not even sure how you can go about estimating it. You'll at least need an arbitrary-precision calculator that can handle huge factorials without dying.

Note that the probabilities will follow a curve that starts at nearly 0 when N = 1 or 2, and it will reach 1 when N >= 2^288, similar in shape to the one on the Wikipedia page for the birthday paradox.

The birthday paradox reaches P = .5 when N = 23. In other words, the probability of a collision is 50% when N is 6% of S. If that scales (I'm not sure if it does), it means that there will be a 50% chance of a collision when you have 6% of 2^288 hashes. 6% of 2^288 is around 2^284. Your value of N (several hundred million) is nowhere near that. It's practically insignificant compared to your S, so I don't think you have anything to worry about. Collisions aren't very likely.

Welbog
There's one more assumption: that collisions in MD5 and SHA1 are independent. That is, that the two algorithms behave differently enough that a pair of strings that collide in MD5 are no more likely than usual to collide in SHA1. I think that's a safe assumption, even though the two algorithms have similar design.
Beta
@Beta: Good point. Well worth mentioning.
Welbog
Just to expand on Beta's statement. Welbog's analysis should be taken as a theoretical lower limit, the actual probability is guaranteed to be greater than or equal to that limit. Finding the actual true probability is cryptographically hard, you would actually have to fully crack both MD5 and SHA-1 to prove the actual probability.
Greg Miller
re: last paragraph: it doesn't scale linearly. Birthday paradox P=.5 goes roughly as sqrt(S), although off the top of my head, I can't find a reputable reference that states that.
Jason S
Even if it is sqrt(S), 2^29 is still insignificant compared to 2^144. But I accept that it's probably not linear.
Welbog
+1  A: 

If message size is not restricted, the chance approaches 100% asymptotically, as there's an infinite number of possible messages and a finite number of possible hashes.

(note: edit to question makes this less relevant now)

ceejayoz
No. No matter how large the message is, it still hashes to a single MD5+SHA1 hash.
Captain Segfault
You're missing the point. There are a limited number of possible hashes, as they're finite length. There are an unlimited number of messages. Infinite messages plus finite hashes means infinite collisions.
ceejayoz
I think ceejayoz is missing the point, actually. In the question, it says, "More information: the size of the pool of possible messages is restricted, but large (several hundred million)." That is not the same as infinite.
Fantius
@fantius Question got edited. I even put a note in this answer pointing that out 19 minutes before you commented.
ceejayoz
OK, sorry. I was going based on the time of your last comment, which was after the time of the question edit.
Fantius
ceejayoz, I think this confusion arose because you said "message size" when you meant "the number of messages".
Beta
If message size is not limited, the number of messages is as a result not limited, as I can do "message", "messagemessage", "messagemessagemessage", and so on. Infinite message size logically leads to infinite number of messages.
ceejayoz
+3  A: 
Jason S
darnit, you people keep voting me up when I make typos!
Jason S
A: 

Generally, when one picks N elements randomly it is easier to compute the expected number of collision than the probability of a collision. Since the expected number of collisions cannot be smaller than the probability of a collision it can frequently be used as a suitable upper bound.

Assume that p is the probability that two randomly picked elements collide. If we pick N random elements then there are N*(N-1)/2 pair of elements and hence the expected number of collisions is

p * N * (N-1)/2.

E.g., if we assume that the probability for a collision for both MD5 and SHA1 is p=2-288 then even after randomly picking 2100 elements we still only expect about 2-89 collisions.

Another example: if we pick 230 random elements and only compute the MD5. Assuming that a collision between two MD5 hashes is p=2-128 this gives an expected number of 2-59 for the number of collisions. Hence even the probability that the MD5 hash collides for two inputs is already very small.

Accipitridae