Microsoft has just released four security bulletins on this months' Patch Tuesday fixing vulnerabilities in Microsoft software products. Three of the four bulletins have a maximum severity rating of critical, the highest rated, while one is rated as important.
Affected software includes several Microsoft operating systems and Microsoft Office, take a look at the listing below for additional details on every security bulletin released today.
All vulnerabilities allow remote code execution on compromised systems. Additional information about this months' patches are available at the Technet blog post.
Please click on the following link to open the newsletter signup page: Ghacks Newsletter Sign up
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.
Hoi Martin thanks a lot for this fairy extensive and greatly helpful explanation of this month MS updates. What i really like are the pictures you implemented, ferry handy that i can open them in a new tab.
You are welcome Paulus ;)
Almost everyone is recommending to install the updates, especially if the vulnerabilities are sever and exploitable… Now the question, did anyone of you readers ever become a victim (loose data or have any other problem) from something that could have been avoided if the system were updated???
Somehow I have the feeling that it’s a waste of time to update the operating system all the time…
Crodol, you should always update. The change to become a victim depends on several factors, especially if an exploit is in the wild and how it is targeting computer systems. The worst case is an automated large scale attack. There is obviously a chance that you will never get hit even if you do not update, but then again, I would not want to take that chance.
This information has been released by Microsoft.
http://blogs.technet.com/b/msrc/archive/2010/07/13/july-2010-security-bulletin-release.aspx
And I have linked to it.