文件列表:

isic-0.06\isic-0.06\configure (48239, 2004-11-06)
isic-0.06\isic-0.06\configure.in (683, 2004-11-06)
isic-0.06\isic-0.06\esic.c (8955, 2004-11-07)
isic-0.06\isic-0.06\icmpsic.c (10152, 2004-11-07)
isic-0.06\isic-0.06\INSTALL (1153, 2004-11-11)
isic-0.06\isic-0.06\install-sh (4771, 2004-11-06)
isic-0.06\isic-0.06\isic.c (9404, 2004-11-07)
isic-0.06\isic-0.06\isic.h (265, 2004-11-06)
isic-0.06\isic-0.06\Makefile.in (1239, 2004-11-07)
isic-0.06\isic-0.06\tcpsic.c (11688, 2004-11-07)
isic-0.06\isic-0.06\udpsic.c (10933, 2004-11-07)
isic-0.06\isic-0.06\wrapper.sh (1121, 2004-11-06)
isic-0.06\isic-0.06\ChangeLog (884, 2004-11-11)
isic-0.06\isic-0.06 (0, 2009-05-16)
isic-0.06 (0, 2009-05-16)

ISIC -- IP Stack Integrity Checker by Mike Frantzen 1) Purpose 2) Contributors 3) History 4) Accomplishments 5) Copyright (BSD Style)  1) Purpose ISIC (and components) is intended to test the integrity of an IP Stack and its component stacks (TCP, UDP, ICMP et. al.) It does this by generating a controlled random packet (controlled randomness... wacky huh?). The user can specify he/she/it [I'm tempted to put 'it' before 'she' :-)] wants a stream of TCP packets. He/she/it suspects that the target has weak handling of IP Options (aka Firewall-1). So he/she/it does a 'tcpsic -s rand -d firewall -I100'. And observes the result. A great use for ISIC would be to fire it through a firewall and see if the firewall leaks packets. But of course that would be illegal because Network Associates owns a bogus patent on that :-) You could do that by setting the default route on the sending computer to the firewall..... But that would be illegal. (But I can't legally have a beer so do you think I care about laws?) By far the most common use for these tools is testing IDS systems. A day after I took the source offline and moved it to a cvs server, a half dozen people working on seperate home-grown IDS systems emailed requesting the source be put back up. ISIC is not being actively maintained. I have moved on to bigger and better things (quite larger than this weekend project).  2) Contributors Mike Frantzen The original author Matt Hargett Various Patches Dug Song Various Patches Shu Xiao Current maintainer The idea for ISIC came from two of my co-workers during my summer job: Kevin Kadow Mike Scher  3) History I wrote ISIC v.01 over a two week period on a Redhat 5.1 box. Well, (huddle around kiddies) one weekend I came back from work and turned on the monitor to discover loads of scsi errors. I had the binaries compiled statically on a wee little Trinux floppy. I was able to get the machine partially up and running and got a little bit of the source off. I yanked the harddrive and dropped it in Mike Scher's box (Linux). It fscked (sed s/s/u/g) the drive and I grabbed the lost+found directory. I got the source back. Much to my suprise, large (remarkably block sized) chunks were missing/rearranged across ALL the files. Every linux box I have ever had came back to bite me in the ass. So over a weekend, I rewrote isic, tcpsic, and udpsic. Icmpsic took a bit longer... damn bugs. Total time: 6 hours. Total time on icmpsic after I forgot to add the IP Header length to the pointer to the ip options, 3 hours. Bah. I ***ed up in version 0.02. My Makefile wasn't compatible with future versions of Libnet.... Whoops... My fault. Now we have version 0.03. Hehe, somehow forgot to randomize the TCP flags in 0.03 ;) [Thanks Florian] I stuck esic (ether frame spewer) into the package for 0.04. I had it kicking around so why not toss it in. (Heh, had to redeem myself for the TCP flags ***up)  4) Accomplishments If ISIC finds any vulnerabilities for you, please let me know. I would love to know the product and type of vulnerability. I will withhold the information from this list at your request. If you give me permission to add it to this list, you will get full credit. If you manage a Bugtraq post, I appreciate finding my name in the list of credits :-) ISIC (v0.01) Unreleased version. - During non-extensive testing, it failed to find a vulnerability in Cisco's PIX (4.2?) - Mike Frantzen - Logging vulnerability in Checkpoint Firewall-1 4.0 Could predictably get a packet logged with a different source IP. Unable to reliably and consistently reproduce. (NOT RELEASED) - Mike Frantzen - IP Stack vulnerability in Checkpoint Firewall-1 4.0 Wacky IP packets sometimes descended deep into the rulebase but got caught on drop all rule. Unexploitable. (NOT RELEASED) - Mike Frantzen - Panic of Gauntlet 5.5 Beta (NOT RELEASED) - Mike Frantzen - Lock up Gauntlet 5.5 Beta (NOT RELEASED) - Mike Frantzen - Frag DOS of Gauntlet 5.5 Beta (NOT RELEASED) - Mike Frantzen - Lock up of Gauntlet 5.0 ICMP Parameter Problem packets with IP Options in the encapsulated packet caused Gauntlet to lock up. (BUGTRAQ'd) - Mike Frantzen ISIC (v.02) -- ISIC (v.03) - Remote exploit of Raptor 6.x - CERIAS (BUGTRAQ'd)  5) Copyright -- Modified BSD Source License ISIC is Copyright (c) 1999 Mike Frantzen, Chicago, IL, USA. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：