Endpoint SecurityApplication · Checkpoint

CVE-2023-28133

HIGH · 7.8 CVSS v3.1 Published 2023-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Local privilege escalation in Check Point Endpoint Security Client (version E87.30) via crafted OpenSSL configuration file

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

Local privilege escalation vulnerability in Check Point Endpoint Security Client version E87.30 allows a local attacker to gain elevated privileges by placing a crafted OpenSSL configuration file in a location where the client processes it, potentially leading to SYSTEM-level access.

MitigationApply the vendor-supplied patch or update to Check Point Endpoint Security Client version E87.30 or later; as a workaround, restrict file system permissions on directories where OpenSSL configuration files are stored to prevent unauthorized modification.

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:= e87.30

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify Check Point Endpoint Security Client installation
    Check for the presence of Check Point Endpoint Security Client by looking for its installation directory, typically under C:\Program Files\Checkpoint\Endpoint Security\ or C:\Program Files (x86)\Checkpoint\Endpoint Security\, and list the product version information from the installation.
    Affected if The client software is installed and the version equals exactly E87.30.
  2. Verify the exact installed version
    Check the product version through Windows registry under HKLM\SOFTWARE\Checkpoint\Endpoint Security\Client\Version or by viewing the version information of the main executable file in the installation directory.
    Affected if The version displayed is E87.30 exactly.
  3. Locate OpenSSL configuration files processed by the client
    Search for OpenSSL configuration files (typically named openssl.cnf or .openssl.cnf) within the Check Point Endpoint Security Client installation directory and related data folders such as %PROGRAMDATA%\Checkpoint\Endpoint Security\.
    Affected if OpenSSL configuration files exist in directories owned or used by the Check Point client.
  4. Inspect directory permissions for OpenSSL config locations
    Use icacls or Windows Explorer security properties to review write permissions on directories where OpenSSL configuration files are stored, particularly within the Check Point installation folder and ProgramData\Checkpoint directories.
    Affected if Users without administrative privileges can write to directories containing OpenSSL configuration files used by the client.

You are affected if Check Point Endpoint Security Client version E87.30 is installed AND OpenSSL configuration files exist in client-accessible directories with weak permissions allowing unprivileged modification.

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 the vendor-supplied patch or update to Check Point Endpoint Security Client version E87.30 or later; as a workaround, restrict file system permissions on directories where OpenSSL configuration files are stored to prevent unauthorized modification.

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28133 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28133 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