dbcve.org
Jumbo Hotfix For Endpoint Security ServerApplication · Checkpoint

CVE-2019-8459

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-20
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
Check Point Endpoint Security Client for Windows, with the VPN blade, before version E80.83, starts a process without using quotes in the path. This can cause loading of a previously placed executable with a name similar to the parts of the path, instead of the intended one.

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 · high confidence

Check Point Endpoint Security Client for Windows with the VPN blade before version E80.83 starts processes without quoting path variables. This allows Windows to search for executables in each directory component of the path, enabling an attacker who has write access to any directory in the PATH to plant a malicious binary with a name matching a path component, which will be executed instead of the legitimate intended binary.

MitigationUpgrade Check Point Endpoint Security Client for Windows with VPN blade to version E80.83 or later. Additionally, restrict filesystem write access to directories in the system PATH to prevent binary planting.

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
Jumbo Hotfix For Endpoint Security ServerApplication
Affected:< r77.30
Endpoint Security Server PackageApplication
Affected:< r77.30.03
Smartconsole For Endpoint Security ServerApplication
Affected:< r77.30.03= e80.83
Endpoint Security ClientsApplication
Affected:< e80.83
Remote Access ClientsApplication
Affected:< e80.83
Capsule Docs Standalone ClientApplication
Affected:< e80.82

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check if Check Point Endpoint Security Client is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\CheckPoint\Endpoint Security for installed client components
    Affected if Check Point Endpoint Security Client appears in installed programs
  2. Identify the installed client version
    Right-click the Check Point Endpoint Security tray icon, select 'Help' > 'About', or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\Endpoint Security\Common\Install_Version
    Affected if The version displayed is lower than E80.83 (for Endpoint Security Clients or Remote Access Clients) or lower than E80.82 (for Capsule Docs Standalone Client)
  3. Confirm the VPN blade is enabled
    Open Check Point Endpoint Security Client GUI, go to 'Blades' or 'Configuration' and verify if the VPN blade is active
    Affected if The VPN blade is enabled and the client version is below E80.83
  4. Identify the system PATH directories
    Open Command Prompt and run 'echo %PATH%' to list all directories in the system PATH environment variable
    Affected if One or more directories in the PATH are writable by the current user or a low-privilege account

If Check Point Endpoint Security Client with the VPN blade is installed at a version below E80.83 AND any directory in the system PATH is writable by an untrusted user, the environment is vulnerable to CVE-2019-8459.

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 Endpoint Security Client for Windows with VPN blade to version E80.83 or later. Additionally, restrict filesystem write access to directories in the system PATH to prevent binary planting.

Recommended fix High confidence

E80.83 or later for clients; r77.30.03 or later for server components

  1. Identify the specific Check Point Endpoint Security product in use from the affected products list
  2. For Endpoint Security Clients and Remote Access Clients: Upgrade to version E80.83 or later
  3. For Capsule Docs Standalone Client: Upgrade to version E80.82 or later
  4. For Endpoint Security Server Package: Upgrade to version r77.30.03 or later
  5. For Smartconsole For Endpoint Security Server: Upgrade to version r77.30.03 or later
  6. For Jumbo Hotfix For Endpoint Security Server: Upgrade to version r77.30 or later
  7. Verify the upgrade was successful and the unquoted path issue is resolved

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

Fix this in Jumbo Hotfix For Endpoint Security Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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