{"id":2388,"date":"2006-05-16T00:00:00","date_gmt":"2006-05-16T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/16\/experts-exchange-patch-ok-despite-glitches\/"},"modified":"2021-12-30T11:41:14","modified_gmt":"2021-12-30T11:41:14","slug":"experts-exchange-patch-ok-despite-glitches","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/05\/16\/experts-exchange-patch-ok-despite-glitches\/","title":{"rendered":"Experts: Exchange patch OK, despite glitches"},"content":{"rendered":"<p>Several security companies are urging Windows managers to install the latest Microsoft Exchange Server patch, despite reports that the fix is causing problems for some mobile devices.  &#8220;This is a critical flaw and administrators should test and install the patch as soon as possible,&#8221; said David Litchfield, a U.K.-based security consultant with Next Generation Security (NGS) Software Ltd. &#8220;Until the patch is installed, administrators should consider blocking or quarantining calendar-based mail messages as an interim solution.&#8221;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Symantec Corp., in Cupertino, Calif., warned administrators to patch quickly and listed the Exchange vulnerability level as &#8220;High&#8221; on the company&#8217;s security response Web site.<\/p>\n<p>http:\/\/searchsecurity.techtarget.com\/originalContent\/0,289142,sid14_gci1188468,00.html<\/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-2388","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\/2388","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=2388"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2388\/revisions"}],"predecessor-version":[{"id":4875,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2388\/revisions\/4875"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}