Differences

This shows you the differences between two versions of the page.

View differences: Side by SideInline Go

Link to this comparison view

Both sides previous revisionPrevious revision 2026/05/21 11:53 jp 2026/05/21 09:26 jp 2026/05/21 09:26 jp 2026/05/21 09:23 jp 2026/05/21 09:21 jp 2026/05/21 09:21 jp 2026/05/21 09:09 jp 2026/05/21 09:09 jp 2026/05/21 09:07 jp 2026/05/21 09:05 jp 2026/05/21 09:04 jp 2026/05/21 09:03 jp 2026/05/21 09:01 jp 2026/05/21 09:01 jp createdGo Next revision		Previous revision 2026/05/21 11:53 jp 2026/05/21 09:26 jp 2026/05/21 09:26 jp 2026/05/21 09:23 jp 2026/05/21 09:21 jp 2026/05/21 09:21 jp 2026/05/21 09:09 jp 2026/05/21 09:09 jp 2026/05/21 09:07 jp 2026/05/21 09:05 jp 2026/05/21 09:04 jp 2026/05/21 09:03 jp 2026/05/21 09:01 jp 2026/05/21 09:01 jp createdGo
exchange_emergency_mitigation_service [2026/05/21 09:09] – jp		exchange_emergency_mitigation_service [2026/05/21 11:53] (current) – jp
Line 25:		Line 25:
	EXCHANGE4               True {PING1, M2.1.0}		EXCHANGE4               True {PING1, M2.1.0}
	</code>		</code>
		+
		+	Статус защиты с помощью данной службы можно проверить также, используя скрипт //Exchange Health Checker//.
	Уязвимость **CVE-2026-42897** - как раз хороший пример случая обработки проблемы с //Exchange Emergency Mitigation Service//. Для проверки - была ли устранена данная уязвимость при работающей службе //Exchange Emergency Mitigation Service//, требуется сделать следующее.		Уязвимость **CVE-2026-42897** - как раз хороший пример случая обработки проблемы с //Exchange Emergency Mitigation Service//. Для проверки - была ли устранена данная уязвимость при работающей службе //Exchange Emergency Mitigation Service//, требуется сделать следующее.
-	1. Качаем скрипт Exchange Health Checker:	+	1. Качаем //Exchange On-premises Mitigation Tool (EOMT)//:
		+
		+	https://microsoft.github.io/CSS-Exchange/Security/EOMT/
		+
		+	2. Выполняем на сервере Exchange
		+
		+	.\EOMT.ps1 -ShowMitigationStatus
		+	3. Выбираем нужную уязвимость в списке и проверяем статус. Если //mitigation// механизм был применен, увидем что-то в духе:
		+
		+	<code>
		+	Checking mitigation status for CVE-2026-42897 on EXCH1
		+	EXCHANGE1 : Code Fix Applied: False | Mitigation Applied: True
		+	</code>
		+
		+	:!: Данная служба обычно применяет некие экстренные хотфиксы, которые могут нарушать штатную работу каких-либо компонентов. К примеру, для **CVE-2026-42897** этот список приличный.
		+
		+	<code>
		+	Known issues when mitigation is applied
		+	We are aware of following known issues once CVE-2026-42897 mitigation is applied (using either option above):
		+
		+	OWA Print Calendar functionality might not work. As a workaround copy the data or screenshot the calendar you want to print or use Outlook Desktop client.
		+	Inline images might not display correctly in the recipients OWA reading pane. As a workaround, send images as email attachments or use Outlook Desktop client.
		+
		+	OWA light (OWA URL ending in /?layout=light) does not work properly. Please note that this feature has been deprecated several years ago and is not intended for regular production use.
		+	OWACalendar.Proxy healthset might start showing unhealthy once the mitigation is in effect. This can cause alerts if you use various monitoring solutions for your Exchange Server. If you see this problem, we recommend ignoring those alerts within your monitoring platform until the fix is out and mitigation is removed.
		+
		+	Published calendars might not work with error 500.
		+	We are aware of the mitigation showing the "Mitigation invalid for this exchange version." in mitigation details. This issue is cosmetic and the mitigation DOES apply successfully if the status is shown as "Applied". We are investigating on how to address this.
		+	</code>
		+
		+	https://techcommunity.microsoft.com/blog/exchange/addressing-exchange-server-may-2026-vulnerability-cve-2026-42897/4518498
-	https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/	+	{{tag>Exchange Microsoft Mail PowerShell CVE}}