Re: [Full-disclosure] Microsoft Windows TCP/IP Timestamps Code Execution Vulnerability

[Ivan Security <ivanchukl@xxxxxxxxx>]

Binary diffing?. Stop spamming.
We already know that it's a timestamp issue. Do you have any idea to start
some research/test?. I was reading the RFC 1323 and a paper about TCP/IP
implementation in Windows 2003 Server but it seems to be very reliable. I
mean, how windows implemented it to lead to code execution?.

2009/11/27 webDEViL <w3bd3vil@xxxxxxxxx>

> That's what binary diffing is all about.
>
> Sent from my iPhone
>
>
> On Nov 27, 2009, at 7:59 AM, Ivan Security <ivanchukl@xxxxxxxxx> wrote:
>
>  Hi list,
>>
>> Has anyone more details about this vulnerability?. The advisory just say:
>> "The vulnerability exists due to the TCP/IP stack not cleaning up state
>> information correctly. This causes the TCP/IP stack to reference a field as
>> a function pointer when it actually contains other information"
>> I'd like to know a bit more in order to test it and make some research.
>>
>> Regards,
>>
>> Ivan.
>> _______________________________________________
>> Full-Disclosure - We believe in it.
>> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>> Hosted and sponsored by Secunia - http://secunia.com/
>>
>

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/