{"id":2389,"date":"2006-05-26T00:00:00","date_gmt":"2006-05-26T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/26\/exploit-of-windows-2000-zero-day-to-hit-in-june\/"},"modified":"2021-12-30T11:41:15","modified_gmt":"2021-12-30T11:41:15","slug":"exploit-of-windows-2000-zero-day-to-hit-in-june","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/26\/exploit-of-windows-2000-zero-day-to-hit-in-june\/","title":{"rendered":"Exploit Of Windows 2000 Zero-Day To Hit In June"},"content":{"rendered":"<p>Symantec warned its enterprise customers that an unpatched vulnerability in Windows 2000&#8217;s file sharing protocol has surfaced, with details of an exploit expected to show next month.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>By Immunity researcher Dave Aitel&#8217;s account, the exploit leverages a flaw in the operating system&#8217;s kernel that can be triggered through SMB, and will give an attacker full access to the PC.  &#8220;An official security update from Microsoft will likely not be in development until after June when the information is released.&#8221;<\/p>\n<p>Windows 2000 was last patched against an SMB vulnerability in June 2005.<\/p>\n<p>http:\/\/www.informationweek.com\/security\/showArticle.jhtml;jsessionid=XQQITZ21JK35MQSNDBECKICCJUMEKJVN?articleID=188500259<\/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-2389","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\/2389","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=2389"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2389\/revisions"}],"predecessor-version":[{"id":4876,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2389\/revisions\/4876"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2389"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2389"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2389"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}