{"id":455,"date":"2003-10-29T00:00:00","date_gmt":"2003-10-29T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/10\/29\/microsoft-to-switch-off-spam-plagued-windows-messenger\/"},"modified":"2021-12-30T11:37:21","modified_gmt":"2021-12-30T11:37:21","slug":"microsoft-to-switch-off-spam-plagued-windows-messenger","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2003\/10\/29\/microsoft-to-switch-off-spam-plagued-windows-messenger\/","title":{"rendered":"Microsoft To Switch Off Spam-Plagued Windows Messenger"},"content":{"rendered":"<p>Microsoft said Tuesday that it would turn off the spam- and vulnerability-plagued Windows Messenger Service in the next update to Windows XP.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Not to be confused with the instant messaging service with a similar name, Windows Messenger Service is used primarily by enterprises to send pop-up text messages to alert users of such events as impending server shutdowns.<\/p>\n<p>Service Pack 2 for Windows XP, which is expected by the middle of 2004, will turn off the service by default.<\/p>\n<p>Current editions of Windows XP have it enabled.<\/p>\n<p>Windows Messenger Service has been exploited by spammers, and security vulnerabilities that can be exploited by attackers have been recently noted by Microsoft.<\/p>\n<p>More info: [url=http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=V2GPYY5VZ1PW2QSNDBCSKHQ?articleId=15800063]http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=V2GPYY5VZ1PW2QSNDBCSKHQ?articleId=15800063[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-455","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/455","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=455"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/455\/revisions"}],"predecessor-version":[{"id":2942,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/455\/revisions\/2942"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=455"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=455"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}