CVE-2014-8951
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 · uneditedUnspecified vulnerability in Check Point Security Gateway R75, R76, R77, and R77.10, when UserCheck is enabled and the (1) Application Control, (2) URL Filtering, (3) DLP, (4) Threat Emulation, (5) Anti-Bot, or (6) Anti-Virus blade is used, allows remote attackers to cause a denial of service (fwk0 process crash, core dump, and restart) via a redirect to the UserCheck page.
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 confidenceCheck Point Security Gateway R75-R77.10 contains an unspecified vulnerability when UserCheck is enabled along with Application Control, URL Filtering, DLP, Threat Emulation, Anti-Bot, or Anti-Virus blades. Remote attackers can trigger a denial of service via a redirect to the UserCheck page, causing the fwko0 process to crash, generate a core dump, and restart.
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= r75= r76= r77= r77.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Check Point Gateway versionRun 'cpstat -f version os' or 'fw ver' to retrieve the installed gateway versionAffected if Version is r75, r76, r77, or r77.10 - other versions are not affected
-
Verify if UserCheck is enabledCheck the gateway configuration via SmartConsole under UserCheck settings, or query the policy installation status using 'cpwd_admin list' to confirm UserCheck daemon is runningAffected if UserCheck is active/running on the gateway
-
Confirm enabled security bladesReview active blades in SmartConsole under Gateway > Security Policy, or run 'cpstat -f blades all' to list enabled bladesAffected if Any of these blades are enabled: Application Control, URL Filtering, DLP, Threat Emulation, Anti-Bot, or Anti-Virus
-
Check for fwko0 process crashesSearch for core dump files in /var/log/dump/usermode/ or review system logs for 'fwko0' crash events using 'grep -i fwko0 /var/log/messages'Affected if Recent fwko0 process crashes or core dumps are found after external redirects to UserCheck page
Environment is affected if the gateway runs version R75, R76, R77, or R77.10 with UserCheck enabled simultaneously with at least one of Application Control, URL Filtering, DLP, Threat Emulation, Anti-Bot, or Anti-Virus blades.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable UserCheck or the affected security blades (Application Control, URL Filtering, DLP, Threat Emulation, Anti-Bot, Anti-Virus) until a vendor patch is applied. Consider network segmentation to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-8951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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