Vulnerability Database

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "firewall--1"

Found 1 matching product.

You can search for specific versions with /product/firewall--1/1.2.3

checkpoint / firewall-1

43 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium July 27, 2006 7/27/06
== r55w
== r55w-hfa2
== r55w-hfa1
High November 18, 2005 11/18/05
== 3.0
High December 31, 2004 12/31/04
== 4.1-sp1
== 4.1-sp5
== 4.0-sp2
== 4.0-sp6
== 4.1-sp3
== 4.0-sp3
== 4.1-sp6
== 4.0-sp7
== 4.0-sp4
== 4.1-sp5a
== 4.1
== 4.1-sp4
== 4.0-sp5
== 4.0-sp8
== 4.0
== 4.0-sp1
== r55
== 4.1-sp2
High November 23, 2004 11/23/04
*
== 2.0
== next_generation_fp0
== next_generation_fp1
== next_generation_fp2
Medium November 23, 2004 11/23/04
*
== 2.0
== next_generation_fp0
== next_generation_fp1
== next_generation_fp2
Medium November 23, 2004 11/23/04
*
== 2.0
== next_generation_fp0
== next_generation_fp1
== next_generation_fp2
High September 28, 2004 9/28/04
== 4.1-sp6
High July 7, 2004 7/7/04
== 2.0
*
== 2.0.1
High March 3, 2004 3/3/04
*
High March 3, 2004 3/3/04
== 4.1-sp1
== 4.1-sp5
== next_generation_fp1
== 4.1-sp3
== 4.1-sp5a
== 4.1
== 4.1-sp4
== next_generation_fp0
== 4.1-sp2
Medium October 20, 2003 10/20/03
== 4.1
== 4.0
Low December 31, 2002 12/31/02
== 4.1
== ng
High August 12, 2002 8/12/02
== 4.1-sp1
== 4.1-sp5
== 4.0-sp2
== 4.0-sp6
== 4.1-sp3
== 4.0-sp3
== 4.0-sp7
== 4.0-sp4
== 4.1
== 4.1-sp4
== 4.0-sp5
== 4.0-sp8
== 4.0
== 4.0-sp1
== 4.1-sp2
High April 1, 2002 4/1/02
== 3.0b
Medium October 8, 2001 10/8/01
== 4.1-sp5
== 4.1-sp3
== 4.1-sp4
High September 21, 2001 9/21/01
== 4.1
== 4.0
Medium September 8, 2001 9/8/01
== 3.0
== 4.1-sp1
== 4.1
== 4.0
== 4.1-sp2
Medium September 8, 2001 9/8/01
== 3.0
== 4.1-sp1
== 4.1
== 4.0
Medium August 31, 2001 8/31/01
*
Medium July 18, 2001 7/18/01
== 4.1-sp1
== 4.1-sp3
== 4.1
== 4.1-sp4
== 4.0
== 4.1-sp2
High July 12, 2001 7/12/01
== 4.1-sp1
== 4.1-sp3
== 4.1
== 4.1-sp2
High July 9, 2001 7/9/01
== 4.1_build_41439
== 4.1
== 4.1-sp2
Medium March 26, 2001 3/26/01
== 4.1-sp3
== 4.1
== 4.1-sp2
High February 12, 2001 2/12/01
== 4.1-sp2
Medium December 11, 2000 12/11/00
== 3.0
== 4.0
High December 11, 2000 12/11/00
== 3.0
== 4.1
== 4.0
High November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
High November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
Medium November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
High November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
High November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
Medium November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
Medium November 14, 2000 11/14/00
== 3.0
== 4.1
== 4.0
High October 20, 2000 10/20/00
== 3.0
== 4.1
== 4.0
Medium June 30, 2000 6/30/00
== 4.1
== 4.0
Medium June 6, 2000 6/6/00
== 4.1
== 4.0
Medium March 11, 2000 3/11/00
== 3.0
== 4.1
== 4.0
High February 12, 2000 2/12/00
== 3.0
== 4.0
High January 29, 2000 1/29/00
== 3.0
High October 20, 1999 10/20/99
== 4.0
Medium August 9, 1999 8/9/99
== 3.0
== 4.0
Low July 29, 1999 7/29/99
== 3.0
== 4.0
High May 11, 1998 5/11/98
*

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.