CVE-2020-6013
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 · uneditedZoneAlarm Firewall and Antivirus products before version 15.8.109.18436 allow an attacker who already has access to the system to execute code at elevated privileges through a combination of file permission manipulation and exploitation of Windows CVE-2020-00896 on unpatched systems.
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 confidenceZoneAlarm Firewall and Antivirus products before version 15.8.109.18436 contain a privilege escalation vulnerability where an attacker with existing system access can manipulate file permissions in combination with exploiting Windows CVE-2020-00896 on unpatched systems to execute code with elevated privileges.
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.109.18436CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 product is installedOpen Programs and Features (appwiz.cpl) or use 'Get-ItemProperty' in PowerShell to list installed software, looking for entries containing 'ZoneAlarm' or 'Check Point'Affected if No ZoneAlarm product is found in the installed programs list
-
Identify the specific ZoneAlarm product versionIn Programs and Features, select the ZoneAlarm entry and view the version, or run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*ZoneAlarm*'} | Select-Object DisplayName, DisplayVersionAffected if Version cannot be determined or the product is not listed
-
Compare installed version to affected rangeCompare the displayed version number to 15.8.109.18436 - any version lower than 15.8.109.18436 is affectedAffected if Installed version is less than 15.8.109.18436 (for example, 15.8.109.18000 or earlier)
-
Verify Windows CVE-2020-00896 patch statusCheck if the Windows system has the security update for CVE-2020-00896 installed by running 'Get-HotFix' or checking Windows Update history for the relevant security patchAffected if Windows system lacks the CVE-2020-00896 patch (KB4557938 or later) AND ZoneAlarm version is below 15.8.109.18436
A user is affected if they have ZoneAlarm Extreme Security installed with a version lower than 15.8.109.18436 AND their Windows system is missing the CVE-2020-00896 patch, as the vulnerability requires both conditions to be exploitable.
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.109.18436
Update ZoneAlarm products to version 15.8.109.18436 or later, and ensure Windows systems are patched against CVE-2020-00896.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6013 — 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-6013 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