We will update issues on this page for about a week or so as they evolve.We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY

(*): ISC rating

We use 4 levels:

PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.

Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.

Important: Things where more testing and other measures can help.

Less Urgent: Typically we expect the impact if left unpatched to be not that big a deal in the short term. Do not forget them however.

The difference between the client and server rating is based on how you use the affected machine. We take into account the typical client and server deployment in the usage of the machine and the common measures people typically have in place already. Measures we presume are simple best practices for servers such as not using outlook, MSIE, word etc. to do traditional office or leisure work.

The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threat for affected systems. The rating does not account for the number of affected systems there are. It is for an affected system in a typical worst-case role.

Only the organization itself is in a position to do a full risk analysis involving the presence (or lack of) affected systems, the actually implemented measures, the impact on their operation and the value of the assets involved.

All patches released by a vendor are important enough to have a close look if you use the affected systems. There is little incentive for vendors to publicize patches that do not have some form of risk to them.

(**): The exploitability rating we show is the worst of them all due to the too large number of ratings Microsoft assigns to some of the patches.

------
(***): N/A for pure clients. Any client acting as a print server or sharing a printer should consider this critical.

------
Post suggestions or comments in the section below or send us any questions or comments in the contact form

ABC is running a piece on how theives are stealing barcode data from images that are posted on Social Media web sites [1]. We have covered information disclosure before on the ISC [2] [3] however this could serve as a reminder to be careful what you post! Most importanlty teach your kids. If you want to know more about Securing the Kids, please check out our sister site Securing the Human [4].

I teach my kids, once it's digital treat it like it's public. There is no such thing as a private email

A reader just wrote in and said there is an issue composing and sending emails on Yahoo! Mail web interface. The IMAP Interface still seems to be functioning but compose seems to have an issue. Are any other readers seeing this?

This one kind of slipped by unnoticed over the holidays, but Claudio & company released a new version of the Cuckoo sandbox and it has some some nice new features. Some of the more significant ones to me are:

full memory dumps of the virtual machines

added packages for jar, java applet, and zip files

support for Windows 7 (yippee!!!)

Add to that lots of other improvements and bug fixes (check them out at the link below) and I can't wait to play with it myself. This project is turning into a very nice flexible automated malware analysis tool. If any of our readers have had a chance to try out the new version and want to share their thoughts, please let us know in the comments or via the contact form. If I get a chance to do some serious playing with it before my next shift, I'll try to write up my experiences. In the meantime, kudos to Claudio & company, keep up the good work.