Windows Hyper-V Denial of Service Vulnerability
Missing synchronization in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network.
FAQ
According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability? In this case, a successful attack could be performed from a low privilege Hyper-V guest. The attacker could traverse the guest's security boundary to cause denial of service on the Hyper-V host environment.
Windows Hyper-V Denial of Service Vulnerability
Missing synchronization in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network.
FAQ
According to the CVSS metric, the Hyper-V attack vector is adjacent (AV:A). What does that mean for this vulnerability? Where the attack vector metric is Adjacent (A), this represents virtual machines connected via a Hyper-V Network Virtualization (HNV) logical network. This configuration forms an isolation boundary where the virtual machines within the virtual network can only communicate with each other. In this attack vector, the vulnerable component is bound to the network stack, but the attack is limited to systems configured to use the HNV network.