Check Point Endpoint before version E86.50 failed to protect against specific registry change which allowed to disable endpoint protection b
Noroxi assessment
Priority: Monitor (action score 10/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.6% (FIRST EPSS); higher than 91.4% of all records.
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Check Point Endpoint before version E86.50 failed to protect against specific registry change which allowed to disable endpoint protection by a local administrator.
- Published
- Jul 7, 2022
- Updated
- Jun 17, 2026
- EPSS
- 4.6% · 91th percentile
- CWE
- CWE-470
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| checkpoint | endpoint security | cpe:2.3:a:checkpoint:endpoint_security |
| checkpoint | harmony endpoint | cpe:2.3:a:checkpoint:harmony_endpoint |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- checkpoint endpoint securitye83
- checkpoint endpoint securitye84
- checkpoint endpoint securitye85
- checkpoint endpoint securitye86.10
- checkpoint endpoint securitye86.20
- checkpoint endpoint securitye86.30
- checkpoint endpoint securitye86.40
- checkpoint harmony endpointe83
- checkpoint harmony endpointe84
- checkpoint harmony endpointe85
- checkpoint harmony endpointe86.10
- checkpoint harmony endpointe86.20
- checkpoint harmony endpointe86.30
- checkpoint harmony endpointe86.40
Versions reported by the vendor
Affected version ranges reported by the assigning authority (checkpoint). Independent of NVD's CPE analysis and usually ahead of it.
n/a Enterprise Endpoint Security Windows Clients.
- before E86.50affected
Same product
checkpoint: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-28133Local privilege escalation in Check Point Endpoint Security Client (version E87.30) via crafted OpenSSL configuration file33Monitor
- CVE-2022-23742Check Point Endpoint Security Client for Windows versions earlier than E86.40 copy files for forensics reports from a directory with low pri32Monitor
- CVE-2023-28134Local Privliege Escalation in Check Point Endpoint Security Remediation Service31Monitor
- CVE-2021-30360Users have access to the directory where the installation repair occurs.31Monitor
- CVE-2020-6021Check Point Endpoint Security Client for Windows before version E84.20 allows write access to the directory from which the installation repa31Monitor
- CVE-2019-8452A hard-link created from log file archive of Check Point ZoneAlarm up to 15.4.062 or Check Point Endpoint Security client for Windows before31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-470 · Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.