{"id":8410,"date":"2019-01-26T18:56:11","date_gmt":"2019-01-26T17:56:11","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8410"},"modified":"2022-05-12T06:13:37","modified_gmt":"2022-05-12T04:13:37","slug":"ad-and-exchange-server-vulnerable-via-ews-api","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/01\/26\/ad-and-exchange-server-vulnerable-via-ews-api\/","title":{"rendered":"AD and Exchange Server vulnerable via EWS API"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Schutz.jpg\" width=\"40\" height=\"47\">Another brief information for Exchange administrators. There is an unpatched vulnerability (CVE-2018-8581) on all Exchange Server versions that could be used by remote attackers to take over the machine. <\/p>\n<p><!--more--><\/p>\n<p>On 21 January 2019 Dirk-jan Mollema <a href=\"https:\/\/www.theregister.co.uk\/2019\/01\/25\/microsoft_exchange_domain_admin_eop\/\" target=\"_blank\" rel=\"noopener\">published<\/a> a Proof-of-Concept (PoC) to upgrade to AD administrator via user account on an Exchange server. The Register then <a href=\"https:\/\/www.theregister.co.uk\/2019\/01\/25\/microsoft_exchange_domain_admin_eop\/\" target=\"_blank\" rel=\"noopener\">picked up<\/a> this up in this article. Since then, reports of the vulnerability identified by <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/vulnerability\/CVE-2018-8581\" target=\"_blank\" rel=\"noopener\">CVE-2018-8581<\/a> have been spreading around the internet. I read some articles, saying, that this vulnerability has been known since December 2018. <\/p>\n<p>When I then read about the workaround to deactivating the <em>DisableLoopbackCheck<\/em> registry value, I briefly searched my blog. I noticed that in November 2018 I already blogged about this unpatched vulnerability on all Exchange Server versions. The details, including the registry hack to mitigate the vulnerability has been discussed with my Nov. 2018 article <a href=\"https:\/\/borncity.com\/win\/2018\/11\/20\/vulnerability-in-exchange-server-2010-2019\/\">Vulnerability in Exchange Server 2010-2019<\/a>. Now I've added the information that became public in January 2019. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Another brief information for Exchange administrators. There is an unpatched vulnerability (CVE-2018-8581) on all Exchange Server versions that could be used by remote attackers to take over the machine.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[580,1547],"tags":[869,69],"class_list":["post-8410","post","type-post","status-publish","format-standard","hentry","category-security","category-software","tag-exchange","tag-security"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=8410"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8410\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=8410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=8410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=8410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}