Microsoft Security Advisory (911052): Memory Allocation Denial of Service Via RPC - 1


 
Thread Tools Search this Thread
Special Forums Windows & DOS: Issues & Discussions Security Advisories (RSS) - Microsoft Microsoft Security Advisory (911052): Memory Allocation Denial of Service Via RPC - 1
# 1  
Old 12-24-2007
Microsoft Security Advisory (911052): Memory Allocation Denial of Service Via RPC - 1

Revision Note: Advisory updated to reference a CVE and to clarify that this issue is anonymously exploitable on Windows 2000 Service Pack 4. Advisory Summary:Microsoft is aware of public reports of proof-of-concept code that seeks to exploit a possible vulnerability in Windows 2000 SP4 and Windows XP SP1. This vulnerability could allow an attacker to levy a denial of service attack of limited duration. On Windows XP SP1, an attacker would need to have a valid logon on the system. For Windows XP SP1 users, an attacker must have valid logon credentials to try to exploit this vulnerability. The vulnerability could not be exploited remotely by anonymous users. However, the affected component is available remotely to users who have standard user accounts. In certain configurations, anonymous users could authenticate as the Guest account. Also, customers who have installed Windows XP Service Pack 2 are not affected by this vulnerability. Additionally, customers running Windows Server 2003 and Windows Server 2003 Service Pack 1 are not affected by this vulnerability.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
HYPER-V(4)						   BSD Kernel Interfaces Manual 						HYPER-V(4)

NAME
hv_vmbus -- Hyper-V Virtual Machine Bus (VMBus) Driver SYNOPSIS
To compile this driver into the kernel, place the following lines in the system kernel configuration file: device hyperv DESCRIPTION
The hv_vmbus provides a high performance communication interface between guest and root partitions in Hyper-V. Hyper-V is a hypervisor-based virtualization technology from Microsoft. Hyper-V supports isolation in terms of a partition. A partition is a logical unit of isolation, supported by the hypervisor, in which operating systems execute. The Microsoft hypervisor must have at least one parent, or root, partition, running Windows Server operating system. The virtualization stack runs in the parent partition and has direct access to the hardware devices. The root partition then creates the child partitions which host the guest operating systems. Child partitions do not have direct access to other hardware resources and are presented a virtual view of the resources, as virtual devices (VDevs). Requests to the virtual devices are redirected either via the VMBus or the hypervisor to the devices in the parent partition, which handles the requests. The VMBus is a logical inter-partition communication channel. The parent partition hosts Virtualization Service Providers (VSPs) which com- municate over the VMBus to handle device access requests from child partitions. Child partitions host Virtualization Service Consumers (VSCs) which redirect device requests to VSPs in the parent partition via the VMBus. The Hyper-V VMBus driver defines and implements the interface that facilitate high performance bi-directional communication between the VSCs and VSPs. All VSCs utilize the VMBus driver. SEE ALSO
hv_ata_pci_disengage(4), hv_netvsc(4), hv_storvsc(4), hv_utils(4) HISTORY
Support for hv_vmbus first appeared in FreeBSD 10.0. The driver was developed through a joint effort between Citrix Incorporated, Microsoft Corporation, and Network Appliance Incorporated. AUTHORS
FreeBSD support for hv_vmbus was first added by Microsoft BSD Integration Services Team <bsdic@microsoft.com>. BSD
September 10, 2013 BSD