Share via

Server down, unable to do mitigation,  CVE alert

LH Auction reg admin 0 Reputation points
2025-11-06T03:16:35.9966667+00:00

Server down, unable to do mitigation,  CVE alert for Windows Server

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Ankit Yadav 14,455 Reputation points Microsoft External Staff Moderator
    2025-11-06T04:06:51.1866667+00:00

    Hello @LH Auction reg admin

    We’ll here to assist you with the mitigation for the issue.

    The mitigation and workaround for this issue is listed out here: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59287

    Mitigation:
    Windows Server customers should install the out-of-band update released on October 23, 2025. Windows Servers enrolled into the hotpatch program should install the out-of-band standalone security update released on October 24, 2025.
    Work-around:

    • If you are unable to install the October 23, 2025 out-of-band update, you can take any of the following actions to be protected against this vulnerability: If the WSUS Server Role is enabled on your server, disable it. Note that clients will no longer receive updates from the server if WSUS is disabled.
    • Block inbound traffic to Ports 8530 and 8531 on the host firewall (as opposed to blocking only at the network/perimeter firewall) to render WSUS non-operational. Important: Do NOT undo either of these workarounds until after you have installed the update.

    Also I observed that you have mentioned that the server is down, do you mean to say that you’re unable to connect to your VM and do the mitigation listed above?
    Could you please confirm if you are able to connect to your Windows Server machine via RDP or via Bastion or via Serial Console ?
    If not, here are some troubleshooting options for RDP failure:

    1. Reset Remote Desktop configuration.
    2. Check Network Security Group rules / Cloud Services endpoints.
    3. Review VM console logs.
    4. Reset the NIC for the VM.
    5. Check the VM Resource Health.
    6. Reset your VM password.
    7. Restart your VM.
    8. Redeploy your VM.

    Details about each of the steps can be found out here: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-rdp-connection#troubleshoot-using-the-azure-portal

    Let me know if you are stil stuck so that we can assist you to fix the blockers!!

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.