Home page logo
/

fulldisclosure logo Full Disclosure mailing list archives

Re: Microsoft Windows TCP/IP Timestamps Code Execution Vulnerability
From: Ivan Security <ivanchukl () gmail com>
Date: Fri, 27 Nov 2009 12:27:29 -0300

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 () gmail com>

That's what binary diffing is all about.

Sent from my iPhone


On Nov 27, 2009, at 7:59 AM, Ivan Security <ivanchukl () gmail com> 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/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]