dbcve.org
Endpoint SecurityApplication · Checkpoint

CVE-2022-23742

HIGH · 7.8 CVSS v3.1 Published 2022-05-12
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
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 versions earlier than E86.40 copy files for forensics reports from a directory with low privileges. An attacker can replace those files with malicious or linked content, such as exploiting CVE-2020-0896 on unpatched systems or using symbolic links.

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 versions before E86.40 copies files from a low-privilege directory when generating forensics reports. An attacker with low-level access can replace these files with malicious content or use symbolic links to achieve privilege escalation, potentially exploiting CVE-2020-0896 on unpatched systems.

MitigationUpgrade Check Point Endpoint Security Client for Windows to version E86.40 or later to remediate the insecure file handling in forensics report generation.

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
Endpoint SecurityApplication
Affected:< e86.40

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Check Point Endpoint Security Client is installed
    Open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed software
    Affected if Check Point Endpoint Security Client for Windows appears in the installed programs list
  2. Identify the installed version
    Locate the Check Point Endpoint Security Client version in Programs and Features or via the Check Point software itself (usually found in C:\Program Files\Checkpoint\Endpoint Connect\ or via the client UI under About/Help)
    Affected if The displayed version number is less than E86.40 (for example, E85.x, E86.00 through E86.30, etc.)
  3. Determine if forensics reports have been generated
    Check for recent forensics report files in the Check Point client data directories, typically under %ProgramData%\Checkpoint\Endpoint Connect\ or %APPDATA%\Checkpoint\, or review system logs for forensics-related activity
    Affected if Forensics reports exist in the user-accessible directory or forensics generation has been performed recently
  4. Check CVE-2020-0896 patch status
    Run 'wmic qfe list' or 'Get-HotFix' to list installed Windows patches; look for security updates addressing CVE-2020-0896 (a Windows kernel privilege escalation vulnerability)
    Affected if The system is missing the security update for CVE-2020-0896 and remains unpatched for that related vulnerability

The environment is affected if Check Point Endpoint Security Client for Windows is installed with a version earlier than E86.40 and the forensics report generation feature has been used, especially on systems also missing the CVE-2020-0896 patch.

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 to version E86.40 or later to remediate the insecure file handling in forensics report generation.

Recommended fix Moderate confidence

E86.40

  1. 1. Identify the current version of Check Point Endpoint Security Client for Windows by checking the software or using system information tools
  2. 2. Download Check Point Endpoint Security Client version E86.40 or later from the official Check Point support portal
  3. 3. Apply the upgrade following Check Point's standard upgrade procedures for Endpoint Security clients
  4. 4. Verify the installed version is E86.40 or higher to confirm the remediation
Caveat Review Check Point release notes for any changes to functionality or compatibility requirements before upgrading

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

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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