CVE-2021-30359
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 · uneditedThe Harmony Browse and the SandBlast Agent for Browsers installers must have admin privileges to execute some steps during the installation. Because the MS Installer allows regular users to repair their installation, an attacker running an installer before 90.08.7405 can start the installation repair and place a specially crafted binary in the repair folder, which runs with the admin privileges.
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 confidenceThis is a local privilege escalation vulnerability in Check Point Harmony Browse and SandBlast Agent for Browsers. The MSI installer repair functionality allows regular users to trigger a repair operation, during which an attacker can place a malicious binary in the repair folder that executes with elevated administrator privileges. This enables a standard user to gain SYSTEM-level code execution.
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< 90.08.7405< 90.08.7405CVSS 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.
-
Verify if Check Point Harmony Browse or SandBlast Agent for Browsers is installedOpen Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for entries named 'Checkpoint Harmony Browse' or 'Checkpoint SandBlast Agent for Browsers'Affected if Either product appears in the installed programs list
-
Retrieve the installed product versionRight-click the installed program in Programs and Features and select Properties, or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductGUID} for the DisplayVersion valueAffected if The displayed version is a version number less than 90.08.7405 (e.g., 90.08.xxxx where xxxx is less than 7405, or any earlier major version)
-
Confirm the vulnerable component is presentCheck for the existence of the Check Point browser protection service or check Program Files for a Check Point installation folder (typically named 'Check Point' or similar)Affected if The product is installed and the Check Point browser protection components are present on the system
A user is affected if Check Point Harmony Browse or SandBlast Agent for Browsers is installed with a version number lower than 90.08.7405, as this version introduced the fix for the insecure MSI repair folder manipulation vulnerability.
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.
dbcve · scoped90.08.7405
Upgrade to Harmony Browse/SandBlast Agent for Browsers version 90.08.7405 or later, which addresses the insecure repair folder manipulation.
90.08.7405 or later
- Identify the currently installed version of Harmony Browse or Sandblast Agent for Browsers by opening the application and checking About/Help, or by locating it in Windows Programs and Features
- Navigate to the official Check Point support portal (supportcontent.checkpoint.com) or the Check Point software download center
- Download the fixed version 90.08.7405 or later of the affected product
- Uninstall the current vulnerable version through Windows Control Panel > Programs and Features
- Restart the computer to ensure clean removal of the vulnerable software
- Run the downloaded installer for version 90.08.7405 or later with administrator privileges
- Follow the installation wizard prompts to complete the installation
- Verify the installed version is 90.08.7405 or higher after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30359 — 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-2021-30359 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