dbcve.org
Identity AgentApplication · Checkpoint

CVE-2024-24910

HIGH · 7.3 CVSS v3.1 Developing Published 2024-04-18
Fix available
A fix is available. Upgrade to 4.2.712 or later.
See remediation →
73/100
Remediation priority · Elevated

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 · unedited
A local attacker can erscalate privileges on affected Check Point ZoneAlarm ExtremeSecurity NextGen, Identity Agent for Windows, and Identity Agent for Windows Terminal Server. To exploit this vulnerability, an attacker must first obtain the ability to execute local privileged code on the target system.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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
Identity AgentApplication
Affected:<= r81.070.0000
Zonealarm Extreme Security NextgenApplication
Affected:< 4.2.712

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 4.2.712 or later
Fixed in 4.2.712
Recommended fix Moderate confidence

Identity Agent: r81.070.0001 or later; ZoneAlarm Extreme Security NextGen: 4.2.712 or later

  1. 1. Identify the currently installed Check Point product and version (Identity Agent or ZoneAlarm Extreme Security NextGen) via Windows Control Panel or the application's About/Help section
  2. 2. Navigate to the Check Point Support Portal at support.checkpoint.com
  3. 3. Locate and download the appropriate security update or hotfix for your product: For Identity Agent, obtain version r81.070.0001 or later; For ZoneAlarm Extreme Security NextGen, obtain version 4.2.712 or later
  4. 4. Ensure you have administrator privileges on the target system
  5. 5. Close any running instances of the Check Point application
  6. 6. Execute the downloaded installer or apply the security update
  7. 7. Restart the system if prompted by the installer
  8. 8. Verify the updated version is correctly installed after reboot
Caveat Upgrading security software may require system restart and temporary disabling of real-time protection; ensure compatible Windows version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24910 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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