Yahoo service SQL injection vuln leads to account exposure

Published: 2012-07-13
Last Updated: 2012-07-13 18:23:40 UTC
by Russ McRee (Version: 1)
2 comment(s)

We're a bit slow on the uptake given SANSFIRE, but as you are likely well aware, a SQL injection vulnerability was leveraged to gain access to the Yahoo Voice service which was utilized by attackers to acquire then post login credentials for more than 453,000 user accounts that they said they retrieved in plaintext.

You can download and review the account list for account that may impact you or your organizations here: http://74.208.161.170:81/yahoo-disclosure.tar.gz
 
Related stories:
 
Password analysis of the account list proved what we've all come to expect. "The top five passwords in the stolen batch were "123456," "password," "welcome," "ninja" and "abc123," said David Harley, senior research fellow at security firm ESET."
Ninja = great skill set, bad password. :-)
 
2 comment(s)

2 for 1: SANSFIRE & MSRA presentations

Published: 2012-07-13
Last Updated: 2012-07-13 14:43:15 UTC
by Russ McRee (Version: 1)
0 comment(s)

 It's been a busy week for me having presented OWASP Top 10 Tools and Tactics at SANSFIRE in Washington, DC Tuesday evening 10 July, followed by Evil Through The Lens of Web Logs at the Microsoft Security Response Alliance Summit in Redmond (the other Washington) Thursday morning 12 July.

I had an excellent time in both cases and met some great people. 
The OWASP Top 10 Tools and Tactics talk was for attendees who've spent any time defending web applications as a security analyst, or perhaps as a developer seeking to adhere to SDLC practices, and have utilized or referenced the OWASP Top 10. Intended first as an awareness mechanism, the Top 10 covers the most critical web application security flaws via consensus reached by a global consortium of application security experts. The OWASP Top 10 promotes managing risk in addition to awareness training, application testing, and remediation. To do so, application security practitioners and developers need an appropriate tool kit. As such, this presentation explored tooling, tactics, analysis, and mitigation for each of the Top 10 and is a useful companion for attendees of Kevin (never except his FB friend request) Johnson's Security 542: Web App Penetration Testing and Ethical Hacking.
We had a full house and a lot of fun.
 
The MSRA presentation was a summary of activity related to the SANS Reading Room paper of the same title, and was presented to attendees from the Global Infrastructure Alliance for Internet Safety (GIAIS) working group (shout out to the REN-ISAC crew). 
Abstract:
Web logs can be analyzed with specific attention to Internet Background Radiation (IBR). Two bands of the IBR spectrum include scanning and misconfiguration where details about attacker and victim patterns are readily available. Via web application specific examples this discussion analyzed attacks exhibiting traits, trends, and tendencies from the attacker and victim perspectives. This presentation built on findings to cover parsing and analysis techniques, as well as investigative tactics. Tooling and real examples were included to allow attendees to learn methods that can be utilized against their own logs for detective measures useful in mitigating attacks.
The MSRA copy of the presentation is not published online but you can grab the same presentation from RSA here or watch a short video version of it here.
This work includes major contributions from ISC Handlers Mark Hofman and Rob Danford
 
Let me know if you have any questions, and thanks to all who attended.
Cheers.
 
0 comment(s)

VMWare Security Advisory 12 JUL 2012

Published: 2012-07-13
Last Updated: 2012-07-13 07:02:03 UTC
by Russ McRee (Version: 1)
0 comment(s)

VMSA-2012-0012 is an advisory specific to a VMware ESXi update that addresses several security issues.

This includes an ESXi update to third party component libxml2. The libxml2 third party library has been updated which addresses multiple security issues.

All the details are available here: http://www.vmware.com/security/advisories/VMSA-2012-0012.html

Russ McRee | @holisticinfosec

 

0 comment(s)
ISC StormCast for Friday, July 13th 2012 http://isc.sans.edu/podcastdetail.html?id=2662

Yesterday (not as on the ball as Rob) at SANSFire

Published: 2012-07-13
Last Updated: 2012-07-13 01:29:21 UTC
by Richard Porter (Version: 2)
3 comment(s)

Last night I presented a series of tips and gotchas whilst setting up a home lab for Malware and Packet collection. 

 

Packet and Malware Collection for the Home Network, Research Starts at Home!

- Richard Porter, ISC Handler
- Wednesday, July 11 * 8:15pm - 9:15pm

If you are just getting started in the Information Security Field, or want to practice your packetFu or MalwareFu? A place to start is on the home network! Often at a SANS Conference you will hear the Instructors, Faculty or even the Handlers reply with "Get Written Permission!" With that, you have permission on a network you own. This talk will go over setup, tools, pit-falls and things to be aware of for the home network. This discussion is a useful addition to both Security 503: Intrusion Detection In-Depth and Forensics 610: Reverse Engineering Malware.

 

It was well attended, and thanks for all the kind words. There were so many requests for my presentation and tips that when we recover from SANSFire, I will write another diary on more hints and tips but here are a couple:

 

1 - Roomate/Spouse/KId Alerting: Let them know you will be capturing traffic (Or not )

2 - Power: Check power where your lab is, your home wiring may be in series [1]

 

[1] http://en.wikipedia.org/wiki/Electrical_wiring

 

@packetalien - Twitter

 

And thanks again for all those who attended. Check back for more tips about running a lab at home (along with the Dionaea Virtual machine, when it is more stable.)

 

From SANSfire 2012, signing off!

Signing back on for an UPDATE: @karl thanks!

Tip 2, power, don't overload your circuit. I have dedicated drops at points in my home. As he pointed out, my tip is to not add to much load to one circuit and plan how much you are going to draw.

 

3 comment(s)

Comments


Diary Archives