CVE-2020-6023
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 · uneditedCheck Point ZoneAlarm before version 15.8.139.18543 allows a local actor to escalate privileges while restoring files in Anti-Ransomware.
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 confidenceCheck Point ZoneAlarm Anti-Ransomware component contains a local privilege escalation vulnerability in the file restoration functionality. The flaw allows a local authenticated attacker to elevate privileges by manipulating file restore operations, likely due to insufficient validation during the restore process in versions prior to 15.8.139.18543.
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< 15.8.139.18543CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if ZoneAlarm Anti-Ransomware is installedOpen Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name, VersionAffected if ZoneAlarm Anti-Ransomware appears in the installed programs list
-
Identify the installed version of ZoneAlarm Anti-RansomwareIn Programs and Features, locate the ZoneAlarm entry and note the Version column; alternatively, check the program's About or Help > About section within the applicationAffected if The displayed version number is lower than 15.8.139.18543
-
Confirm the Anti-Ransomware component is presentLook for ZoneAlarm Anti-Ransomware as a separate entry in installed programs, or check for the ZAARService.exe process in Task Manager under ServicesAffected if The Anti-Ransomware component is installed and running
-
Verify file restoration functionality existsOpen the ZoneAlarm Anti-Ransomware interface and check if there is a restore or file recovery feature available in the settings or dashboardAffected if The file restoration or restore quarantine feature is present and accessible
A system is affected if ZoneAlarm Anti-Ransomware is installed with a version lower than 15.8.139.18543 and the file restoration feature is available.
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 data15.8.139.18543
Upgrade ZoneAlarm to version 15.8.139.18543 or later to obtain the vendor patch. If immediate patching is not feasible, limit local user access to the system and monitor for suspicious restore operations.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6023 — 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-2020-6023 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