dbcve.org
Security GatewayApplication · Checkpoint

CVE-2013-7350

HIGH · 10.0 CVSS v2.0 Published 2014-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple unspecified vulnerabilities in Check Point Security Gateway 80 R71.x before R71.45 (730159141) and R75.20.x before R75.20.4 and 600 and 1100 appliances R75.20.x before R75.20.42 have unknown impact and attack vectors related to "important security fixes."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Multiple unspecified vulnerabilities in Check Point Security Gateway 80 R71.x before R71.45 and R75.20.x before R75.20.4 (including 600 and 1100 appliances before R75.20.42) were patched in these point releases. The vulnerabilities have unknown impact and attack vectors as Check Point did not disclose technical details, but the CVSS score of 10 indicates critical severity requiring immediate attention.

MitigationUpgrade Check Point Security Gateway R71.x systems to R71.45 (730159141) or later, and R75.20.x systems to R75.20.42 or later. Alternatively, consider upgrading to a more recent supported release if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Security GatewayApplication
Affected:= r71.00= r71.45= r75.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Check Point Security Gateway product model
    Log into the Check Point gateway via CLI or SmartDashboard and retrieve the hardware model information (such as 80, 600, 1100) using 'show version' or 'cpstat' commands, or check the appliance label
    Affected if The device is a Check Point Security Gateway 80, 600, or 1100 appliance
  2. Retrieve the installed software version
    Execute 'cpinfo -y all' or 'show version' on the gateway CLI, or check the version in SmartDashboard under Gateway properties
    Affected if The software version displayed is R71.x or R75.20.x series
  3. Compare the R71 version against the fixed release
    If the version begins with R71, verify the exact build number - vulnerable versions are R71.00 through R71.44; the fixed version is R71.45 (730159141)
    Affected if The installed R71.x version is earlier than R71.45
  4. Compare the R75.20 version against the fixed release
    If the version begins with R75.20, verify the exact build number - vulnerable versions are R75.20.00 through R75.20.41; the fixed version is R75.20.42
    Affected if The installed R75.20.x version is earlier than R75.20.42

The environment is affected if the Check Point Security Gateway (80, 600, or 1100) is running any R71.x version before R71.45 or any R75.20.x version before R75.20.42.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Check Point Security Gateway R71.x systems to R71.45 (730159141) or later, and R75.20.x systems to R75.20.42 or later. Alternatively, consider upgrading to a more recent supported release if available.

Recommended fix Moderate confidence

R71.45 (730159141) for R71.x; R75.20.4 or R75.20.42 for R75.20.x

  1. 1. Identify the currently installed Check Point Security Gateway version using 'cpstat' or the SmartDashboard/SmartConsole
  2. 2. For R71.x installations: Schedule a maintenance window and upgrade to R71.45 (build 730159141) or later
  3. 3. For R75.20.x installations: Schedule a maintenance window and upgrade to R75.20.4 or later (R75.20.42 recommended for 600/1100 appliances)
  4. 4. Before upgrading, backup the current configuration using 'migrate export' or the WebUI backup function
  5. 5. Review Check Point Upgrade Import/Export documentation (R75.20) for compatibility requirements
  6. 6. Perform the upgrade via SmartUpdate, WebUI, or CLI according to Check Point upgrade procedures
  7. 7. After upgrade, verify the new version is running with 'cpstat' and confirm all services are operational
  8. 8. Test critical firewall policies and VPN connections to ensure normal operation
Caveat Check Point major version upgrades may require policy re-install and can have compatibility impacts with legacy features; test in lab first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data