According to Aylton Souza,CISSP:
>
> Could you please confirm if this happens even if you do not rely on the
> correct snmp community string?
it looks like the bug can only be triggered when using the correct snmp
community strings defined in $FWDIR/conf/snmp.C. This means it probably
can't be used for a DoS attack against the firewall unless some
firewall admin didn't change the defaults 'public' and 'private'. So
let's lean back and relax.
off topic
=========
I think the most promising DoS attacks against a FW-1 still is to
swamp the state table up to the limit. This has been discussed in
length on this list one year ago. CP has released a fix for 3.0
and 4.0. http://www.checkpoint.com/techsupport/alerts/ackdos.html
If 'Accept VPN-1&FW-1 Control Connections' is enabled, using 4.1
SP0 on Solaris it still has been easy to fill up the state table
with the old trick. So far I didn't try again with SP1 but I won't
be surprised if it still works.
Olaf
--
Olaf Selke, [EMAIL PROTECTED], voice +49 5241 80-7069
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
