dbcve.org
Security GatewayApplication · Checkpoint

CVE-2014-8952

HIGH · 7.1 CVSS v2.0 Published 2014-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 R75.40VS, R75.45, R75.46, R75.47, R76, R77, and R77.10, when the (1) IPS blade, (2) IPsec Remote Access, (3) Mobile Access / SSL VPN blade, (4) SSL Network Extender, (5) Identify Awareness blade, (6) HTTPS Inspection, (7) UserCheck, or (8) Data Leak Prevention blade module is enabled, allow remote attackers to cause a denial of service ("stability issue") via an unspecified "traffic condition."

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 denial of service vulnerabilities exist in Check Point Security Gateway R75.40VS through R77.10 when specific security blades (IPS, IPsec Remote Access, Mobile Access/SSL VPN, SSL Network Extender, Identity Awareness, HTTPS Inspection, UserCheck, or Data Leak Prevention) are enabled. Remote attackers can trigger a stability issue via unspecified traffic conditions, causing the gateway to become unavailable.

MitigationApply Check Point vendor patches/hotfixes for this vulnerability. If patches are unavailable, consider network-level filtering to block malicious traffic patterns and ensure redundancy/failover configurations are in place to maintain availability during attacks.

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:= r75.40= r75.45= r75.46= r75.47= r76= r77= r77.10

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:N/C:N/I:N/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 Check Point Security Gateway version
    Run 'fw ver' or 'cpstat -f version os' on the gateway CLI to retrieve the exact installed version. Alternatively, check the version through SmartDashboard by viewing the gateway object properties.
    Affected if The installed version matches r75.40, r75.45, r75.46, r75.47, r76, r77, or r77.10.
  2. Verify if IPS blade is enabled
    Run 'cpconf -m ips' or check through SmartDashboard by opening the gateway object and inspecting the Security Blade status. Confirm if IPS is activated and licensed.
    Affected if IPS blade is enabled on the gateway.
  3. Verify if IPsec Remote Access blade is enabled
    Check through SmartDashboard by opening the gateway object and inspecting the VPN blade settings, or run 'cpstat -f all vpn' to check VPN configuration.
    Affected if IPsec Remote Access blade is enabled on the gateway.
  4. Verify if Mobile Access/SSL VPN blade is enabled
    Run 'cpconf -m mobile_access' or check through SmartDashboard by viewing the gateway object properties under Mobile Access or SSL VPN settings.
    Affected if Mobile Access or SSL VPN blade is enabled on the gateway.
  5. Verify if Identity Awareness, HTTPS Inspection, UserCheck, or Data Leak Prevention blades are enabled
    Check through SmartDashboard by opening the gateway object and inspecting each respective blade configuration under the Security Blade section, or run 'cpconf' to list enabled modules.
    Affected if Any of Identity Awareness, HTTPS Inspection, UserCheck, or Data Leak Prevention blades are enabled on the gateway.

The gateway is affected if it runs version r75.40 through r77.10 AND has at least one of the vulnerable security blades (IPS, IPsec Remote Access, Mobile Access/SSL VPN, SSL Network Extender, Identity Awareness, HTTPS Inspection, UserCheck, or Data Leak Prevention) enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Check Point vendor patches/hotfixes for this vulnerability. If patches are unavailable, consider network-level filtering to block malicious traffic patterns and ensure redundancy/failover configurations are in place to maintain availability during attacks.

Fix this in Security Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8952 — 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-2014-8952 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