full-disclosure - Re[2]: Is Windows TCP/IP source routing PoC code available?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1394628342.20060629170847@SECURITY.NNOV.RU>
Date: Thu Jun 29 14:10:17 2006
From: 3APA3A at SECURITY.NNOV.RU (3APA3A)
Subject: Re[2]: Is Windows TCP/IP source routing PoC
	code available?

Dear Andrey,

 can you give your comments on why vulnerability that looks so dangerous
 according  to  description (remote kernel-level buffer overflow in ICMP
 processing,  according  to  MS) rated "high", not "critical"? Are there
 are  mitigating  factors for Windows 2003 with RRAS enabled or any RRAS
 installation is vulnerable?

 P.S.  last  instruction  I've got was to publish information only after
 vendor's fix. I did :)

--Wednesday, June 28, 2006, 11:01:51 PM, you wrote to 3APA3A@...URITY.NNOV.RU:

?> Hi All,
?> At the request Microsoft I have not published the additional
?> information. I did not think, that the ZARAZA will publish simple POC
?> without my consent but to that to be, that to not pass. Denis you can
?> check up you system simple POC code from a site of the ZARAZA, only if
?> configuration system corresponds Windows 2000 + NAT a server. In all
?> other cases with services RRAS (Routing, VPN, Dialup Access) it will
?> not work.

?> Tuesday, June 27, 2006, 1:28:03 PM, you wrote:

>> Dear Denis Jedig,

>> Simple PoC and original message from Andrey Minaev, dated February, 2006
>> in Russian with short translation to English) are available from

>> http://www.security.nnov.ru/Fnews753.html

DJ>>> As known, Microsoft did announce a security vulnerability concerning an
DJ>>> overflow within the TCP/IP stack implementation when source routing
DJ>>> fields are used:
DJ>>> http://www.microsoft.com/technet/security/bulletin/MS06-032.mspx

-- 
~/ZARAZA
http://www.security.nnov.ru/