Just a day after downplaying the vulnerability that caused it to issue an out-of-cycle patch last week, Microsoft Corp. late yesterday warned customers that exploit code had gone public and is being used in additional attacks. “We’ve identified the public availability of exploit code that now shows code execution for the vulnerability addressed by MS08-067,” said Mike Reavey, operations manager of Microsoft’s Security Response Center, in a post to the MSRC blog Monday evening. “This exploit code has been shown to result in remote code execution on Windows Server 2003, Windows XP, and Windows 2000.”<\/p>\n","protected":false},"excerpt":{"rendered":"
On Tuesday, a company spokesman declined to specify where Microsoft had found the attack code, saying only that the new warning came after Microsoft became “aware of detailed, reliable, public exploit code.”<\/p>\n
“We are aware that people are working to develop reliable public exploit code for the vulnerability,” acknowledged Christopher Budd, a spokesman for the MSRC, in an entry he wrote Sunday.<\/p>\n
Previously, Microsoft said that it discovered the vulnerability after a small number of attacks had resulted in infections by an information-stealing Trojan, which it dubbed “Win32\/MS08067.gen!A” and third-party anti-virus vendors tagged with their own names. “The malware situation remains the same, as we’ve not seen any self-replicating worms, but instead malware that would be classified as Trojans, specifically the malware we discussed when we released the security update on Thursday.”<\/p>\n
http:\/\/www.computerworld.com\/action\/article.do?command=viewArticleBasic&articleId=9118341<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-2416","post","type-post","status-publish","format-standard","hentry","category-warnings"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2416"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2416\/revisions"}],"predecessor-version":[{"id":4903,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2416\/revisions\/4903"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}