Sunbelt Software has a good write-up on a recent spike in 3d screen saver spam. It’s a free screen saver that comes at a price. The malware has been tracked back to a re-emerging malware gang and is a gift that keeps on giving. Looks like Sunbelt is pursuing them hard, so kudos for their efforts. Always handle attachments and links in an e-mail message with extreme care. If you don’t know how to do that, check out page 12 of the US-CERT’s Common Sense Guide to Cyber Security for Small Businesses or any of the other links in the Resources > Awareness & Education section.
The latest dose of monthly medicine from Microsoft includes 4 critical patches for Microsoft Office. You can get the Microsoft details or the SANS Internet Storm Center Handler’s Diary always provides a simplified view highlighting the most serious of the patches with their own ratings. Of this month’s releases, MS08-14 gets a SANS ISC rating of “Patch Now” due to active exploits in the wild.
The Register, among others, reported the release of a tool that allows easy access to a locked workstation. The caveat is that it requires physical access to the Windows computer and is executed by connecting a Linux device to a Windows computer via firewire. The vulnerability has been documented since 2006, but only recently was a tool released to simplify the exploit. As El Reg notes, one wouldn’t think this would be that difficult to repair, but Microsoft has yet to address it. We can argue semantics over whether firewire or the Microsoft implementation of firewire is at fault, but that doesn’t do much for resolving the issue. Due to the need for physical access, I can’t deem this a critical vulnerability, but physical computer security is often as neglected as electronic computer security so it’s still worthy of note.
Another great contribution by SearchSecurity.com: Misconfigured networks create huge security risks. The article says it all in terms of why I’m trying to do what I’m trying to do with EyeIS; my reason for being.
CA has a nice writeup from last month (thanks for the tip Brian) on a jsp vulnerability recently toyed with on the PayPal site. It’s a fine example of good disclosure; identifying a vulnerability, reporting it effectively, receiving prompt resolution and then documenting how it works in an informed and easy to read way. It’s also a scary little hole. If a money changer like PayPal had it and didn’t know about it, chances are others are vulnerable too. Who built your web site and is it using jsp pages? I’ll keep my eyes peeled for any indicators as to how broad this vulnerability may be as I honestly am not sure exactly how utilized jsp pages are these days.