CVE-2020-6024
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 SmartConsole before R80.10 Build 185, R80.20 Build 119, R80.30 before Build 94, R80.40 before Build 415, and R81 before Build 548 were vulnerable to a possible local privilege escalation due to running executables from a directory with write access to all authenticated users.
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 SmartConsole vulnerable versions run executables from a directory writable by all authenticated users, allowing a local attacker to replace legitimate executables with malicious ones and achieve privilege escalation.
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<= r80.10= r80.20= r80.30= r80.40= r81CVSS 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.
-
Confirm SmartConsole installationLook for SmartConsole installation directories, typically under C:\Program Files\Check Point\SmartConsole or C:\Program Files (x86)\Check Point\SmartConsole on Windows systems.Affected if SmartConsole is found installed on the system.
-
Identify installed SmartConsole versionLocate and read the SmartConsole version information, usually found in an About or version file within the SmartConsole installation directory, or check the program's properties in Add/Remove Programs.Affected if The installed version matches r80.10 and below, r80.20, r80.30, r80.40, or r81 exactly.
-
Locate executable directories used by SmartConsoleExamine the SmartConsole installation for directories containing executable files (.exe) that the application runs, particularly looking for directories under the main installation path.Affected if Executable directories exist within the SmartConsole installation path.
-
Verify directory permissions are non-writable for standard usersRight-click on the executable directories within the SmartConsole installation, go to Properties > Security, and check if authenticated users or all users have Write or Modify permissions to these directories.Affected if Authenticated users or standard users have Write or Modify permissions to directories containing SmartConsole executables.
A user is affected if SmartConsole is installed with a version matching r80.10 or earlier, r80.20, r80.30, r80.40, or r81, and executable directories within the installation are writable by authenticated users.
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 dataUpgrade SmartConsole to R80.10 Build 185 or higher, R80.20 Build 119 or higher, R80.30 Build 94 or higher, R80.40 Build 415 or higher, or R81 Build 548 or higher.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6024 — 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-6024 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