Reported by SANS ISC:
Distributed SSH Brute Force Attempts on the rise again
SSH brute force attempts seem to be on the rise again, at the SANS Internet Storm Center we have received a number of reports that a number of networks are seeing them. The source IP addresses vary with each new attempted username in the wordlist, which would indicate that the attempts are distributed through botnet(s). It only takes a single user with a weak password for a breach to occur, then with that foothold escalation and further attacks are likely next. This is certainly not a new phenomenon, however I think it is a good time to raise awareness about it once again.
This is an online log of my Slackware experiences. Be aware that I'm also using this blog to cover basic and intermediate security issues that may not pertain to Slackware. This is my way of consolidating blogs (I've several of them).
Showing posts with label SANS. Show all posts
Showing posts with label SANS. Show all posts
Friday, June 18, 2010
Saturday, January 30, 2010
SANS Article -- Weathering the Storm Part 2
Weathering the Storm Part 2 @ http://blogs.sans.org/appsecstreetfighter/2010/01/29/weathering-the-storm-part-2-a-day-of-weblogs-at-the-internet-storm-center/
This is pretty cool. This article describes how to parse web server logs for RFI (remote file inclusion). It actually pinpoints the URLs that contain the malicious code.
At first I had an issue in following the logic of the write-up, but when I looked at the scripting, I edited it slightly and used the following:
Yeah, I unzipped the .gz files so that I could have the script parse ALL of the access logs. The result is here.
For people who want to perform forensics on these URLs, have at it but note that some of the links may be old and may no longer exist (or may be blocked or purposely taken down).
This is pretty cool. This article describes how to parse web server logs for RFI (remote file inclusion). It actually pinpoints the URLs that contain the malicious code.
At first I had an issue in following the logic of the write-up, but when I looked at the scripting, I edited it slightly and used the following:
cat access_log | cut -f2 -d'"' access_log* | grep '=http' | grep -v 'utmr=http' | sed 's/.*=http/http/' | uniq -c | sort -rn > /root/WTSP2.txt
Yeah, I unzipped the .gz files so that I could have the script parse ALL of the access logs. The result is here.
For people who want to perform forensics on these URLs, have at it but note that some of the links may be old and may no longer exist (or may be blocked or purposely taken down).
Subscribe to:
Posts (Atom)