XML TXS Windows Server 0Day Dos Exploit

The vulnerability was triggered when the client open  multiple sockets and send data/buffer (A*30017)  and closed socket before handle new socket.
So the server didn't have time to close the connection
then the software crach so its a clean "DOS Exploit"

Tested on Windows XP SP3

(This vulnerability was found using custom XML Fuzzer i coded .... )

--------- ERROR OUTPUT ---------
Unhandled Exception: Unhandled Exception: System.IO.IOException: Unable to write
data to the transport connection: An existing connection was forcibly closed by
the remote host. ---> System.Net.Sockets.SocketException: An existing connectio
n was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, So
cketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Flush()
at Txs.HttpClient.Error(Int32 status, String message)
at Txs.HttpClient.Execute()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()