Pushdo Update

Published: 2010-02-02
Last Updated: 2010-02-14 06:13:05 UTC
by Johannes Ullrich (Version: 2)
1 comment(s)

As mentioned in an older diary [1], "www.sans.org" is one of the targets singled out by the Pushdo bots. At this point, it is not clear what the intention is of the this botnet. If its intention is a denial of service attack, then it failed. It does not appear that any of the sites listed experiences significant Pushdo related outages. We reported earlier about a Bank of America outage, but in hindsight, this outage appears to be unrelated to Pushdo and has been resolved.

We took the opportunity presented by pushdo attacking "www.sans.org", and collected some traffic for further analysis. www.sans.org receives a good amount of legitimate https traffic as well, which made isolating the Pushdo traffic a bit challenging. We focused on a slice of about 10 minutes worth of traffic to ease analysis.

I used the following two snort rules to isolate the traffic:

alert tcp $HOME_NET 443 -> $EXTERNAL_NET any (flow:from_server,established; content: "|15 03 00|"; depth: 3; msg: "SSL 3 Illegal Parameter"; sid: 1000001)
alert tcp $EXTERNAL_NET any -> $HOME_NET 443 ( msg:"Pushdo DoS Request - July 17, 1970 timestamp"; flow:to_server,established; content:"|16|";
     depth:1; content:"|01|"; within:6; content:"|01 01 01 01|"; within:16; sid:10000002;)

One pattern Pushdo exhibits is the use of malformed SSL Helo requests after the TCP connection is established. The server will respond to these requests with an SSL error. The first rule tries to match the SSL error, while the second rule looks for the Pushdo request.

The most aggressive pushdo infected hosts appear to establish a connection about once a minute. We identified about 10k host attacking www.sans.org. According to some reports, Pushdo will also just establish a TCP connection, and then just sit without actually sending the SSL Helo message. 

All this is consistent with Pushdo being a simple DDoS bot. The impact is limited at this point, in part due to the firepower of the botnet being spread across a large number of targets. For more details on Pushdo, see Shadowserver's blog posting [2].

[1] http://isc.sans.org/diary.html?storyid=8125
[2] http://www.shadowserver.org

Johannes B. Ullrich, Ph.D.
SANS Technology Institute

Keywords: bot ddos pushdo
1 comment(s)


So this is pre-encrypted traffic since it's a helo msg right?

Those sigs look to be recipes for false positives. Do you have an IP range you can close it in on?

Diary Archives