Bad russian exit node attacks connections to Wikipedia

I detected a man-in-the-middle attack due to a bad exit node.

While connecting encryptedly to a web page of Wikipedia, the TorBrowser produces a SSL certificate warning.

Name of the exit node: Unnamed IP address: 176.99.10.92 Location: Russia

CN: main.authority.com O: Main Authority OU: Certificate Management

Issued on: 03/14/2013 Expires on: 03/14/2014

SHA1 fingerprint: 0C:FF:4C:A3:5E:F3:A7:64:20:1F:55:0B:32:3F:96:81:91:65:0F:ED MD5 fingerprint: 65:EE:3C:09:75:0D:E5:32:22:2F:0B:3C:7D:8C:A4:72

changed milestone to %Tor: unspecified

added bad-exit component::core tor/tor milestone::Tor: unspecified priority::high resolution::fixed status::closed tor-auth type::defect labels

Trac:
false_certificate.pem

mitm certificate

does not only target wikipedia.

No one interested so far?

Here is another bad exit node:

"Unnamed" 178.250.246.37 (Russia)

It uses a false certificate for intercepting connections to Twitter for example.

SHA1 27:ED:C9:87:EF:5A:25:05:D9:54:F5:A4:3A:48:E0:6B:91:00:65:18

MD5 01:0A:37:56:06:2A:7E:28:E7:8E:E3:E7:B8:FB:2D:DE

CN: main.authority.com O: Main Authority OU: Certificate Management

another "cypherpunks" account user here --

yeah, i've been getting three of these main.authority.com things the last two days. one wikipedia, one a popular blog, one i forgot. i'm attaching another one of these false certificates.

a related question, how do you find out which exit node is responsible when torbrowser gives you a ssl warning?

Trac:
false_certificate_2.pem

We added the badexit flag to 176.99.10.92 two days ago.

Interestingly, I'd already added it to 178.250.246.37 on March 6 on moria1, but tor26 and turtles hadn't because they weren't convinced. I think I just got tor26 to add it.

This is certainly a growing problem -- a particular entity is running many fast exits, many in Russia but not all, and doing this mitm thing. We might have to consider further steps in the arms race (the eventual step is to establish a strong social network between exit relay operators, but it would be good to put that off a while more).

Replying to cypherpunks:

a related question, how do you find out which exit node is responsible when torbrowser gives you a ssl warning?

The best answer I've got, I'm afraid, is to rush over to the network map view and see what your circuit is that has that stream attached to it.

Trac:
Priority: blocker to major

Ok to close? Or are there more? :)

arma: i'm using tor browser without vidalia. is there anything narrower than "GETINFO circuit-status"?

You're using tor browser without vidalia? How odd.

getinfo circuit-status and then getinfo stream-status and then you can match them up. Assuming your browser hasn't hung up yet.

That said, if you're talking to the control port directly, listen to circ and stream events, and then you'll have a log of what happened in the past, which is even better.

Trac:
Keywords: N/A deleted, bad-exit tor-auth added

Trac:
Milestone: N/A to Tor: unspecified

Closing since the exit relay was given the badexit flag.

Trac:
Status: new to closed
Resolution: N/A to fixed

closed

mentioned in issue #8682 (moved)

moved to tpo/core/tor#8657 (closed)