Onderwerp: Update - CheckPoint Vulnerabilities

Whilst examining what was going on in the world of security, I came across
an update by Checkpoint in regards to some recently reported vulnerabilities
in their products, specifically CheckPoint FW-1 and CheckPoint VPN-1.

For more info - http://www.checkpoint.com/corporate/iss.html

Mark

I am not, nor is NGS a partner of Checkpoint, so we were not privy to the
'partners security' bulletin.. I would be interested however in seeing the
full posting by Checkpoint.

Mark

----- Original Message -----
From: "Nicob" <nicob@nicob.net>
To: "Mark Litchfield" <mark@ngssoftware.com>
Cc: <bugtraq@securityfocus.com>
Sent: Thursday, February 12, 2004 10:48 AM
Subject: Re: Update - CheckPoint Vulnerabilities


> On Wed, 2004-02-11 at 19:51, Mark Litchfield wrote:
> > Whilst examining what was going on in the world of security, I came
across
> > an update by Checkpoint in regards to some recently reported
vulnerabilities
> > in their products, specifically CheckPoint FW-1 and CheckPoint VPN-1.
> >
> > For more info - http://www.checkpoint.com/corporate/iss.html
>
> In the Security Bulletin sent to their partners, Checkpoint had some
> strong words against the way ISS released these advisories :
>
>
> ISS' negligence, combined with a
> blatant attempt to market their
> products resulted in the public
> release of the following inaccurate
> statements [...]
>
>
> --
> Nicob <nicob@nicob.net>
>
>
>

On Wed, 2004-02-11 at 19:51, Mark Litchfield wrote:
> Whilst examining what was going on in the world of security, I came across
> an update by Checkpoint in regards to some recently reported vulnerabilities
> in their products, specifically CheckPoint FW-1 and CheckPoint VPN-1.
>
> For more info - http://www.checkpoint.com/corporate/iss.html

In the Security Bulletin sent to their partners, Checkpoint had some
strong words against the way ISS released these advisories :


ISS' negligence, combined with a
blatant attempt to market their
products resulted in the public
release of the following inaccurate
statements [...]


--
Nicob <nicob@nicob.net>