dbcve.org
SmartconsoleApplication · Checkpoint

CVE-2024-24915

HIGH · 7.2 CVSS v3.1 Published 2025-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
Credentials are not cleared from memory after being used. A user with Administrator permissions can execute memory dump for SmartConsole process and fetch them.

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 · moderate confidence

In Check Point SmartConsole, authentication credentials are retained in process memory after use. A user with Administrator privileges can dump the SmartConsole process memory (using tools like procdump) and extract cleartext credentials from the memory dump, enabling privilege escalation or credential theft.

MitigationApply vendor patch when available. Until then, restrict Administrator access to endpoints running SmartConsole, monitor for process memory dump tools (e.g., procdump, dumpert), and consider using dedicated privileged access workstations for SmartConsole sessions.

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
SmartconsoleApplication
Affected:= r81.10= r81.20= r82

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SmartConsole is installed
    Locate SmartConsole installation directory or check for SmartConsole executable (typically in C:\Program Files\CheckPoint\SmartConsole or similar)
    Affected if SmartConsole is installed on the system
  2. Determine installed SmartConsole version
    Right-click SmartConsole.exe, select Properties, then view the Details tab for version information; or run SmartConsole and check Help > About
    Affected if Version displayed is r81.10, r81.20, or r82
  3. Compare version against affected range
    Match the identified version number to the affected versions: r81.10, r81.20, or r82
    Affected if Installed version matches exactly r81.10, r81.20, or r82
  4. Identify if credentials were recently used in SmartConsole
    Check if SmartConsole process (SmartConsole.exe) is currently running or was running recently, indicating active or recent authentication sessions
    Affected if SmartConsole process has been running with active user sessions
  5. Monitor for memory dump tool usage
    Review system logs, EDR alerts, or process monitoring for execution of memory dump utilities (procdump, dumpert, or similar tools) targeting SmartConsole.exe
    Affected if Memory dump tools have been used to capture SmartConsole process memory

Your environment is affected if SmartConsole is installed with version r81.10, r81.20, or r82 and credentials have been used in active sessions, particularly if evidence exists of memory dump tools targeting the SmartConsole process.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available. Until then, restrict Administrator access to endpoints running SmartConsole, monitor for process memory dump tools (e.g., procdump, dumpert), and consider using dedicated privileged access workstations for SmartConsole sessions.

Recommended fix Moderate confidence

r82.40 or later (contact Check Point Support for specific patched version)

  1. Check your current SmartConsole version by opening SmartConsole and going to Help > About
  2. Download the latest SmartConsole version from the Checkpoint Support Portal (support.checkpoint.com) or use Check Point Infinity Portal for management. Note: As of the disclosure date, Check Point has released patches for this vulnerability. Contact Check Point Technical Support to obtain the specific patch/hotfix for your version if upgrading to the latest release is not immediately feasible.
  3. Backup your current SmartConsole configuration and any local settings.
  4. Uninstall the current SmartConsole version from the workstation.
  5. Install the updated SmartConsole version (r82.40 or later recommended, or the specific patched version provided by Check Point support).
  6. Verify the installation and confirm credentials are no longer retained in memory after use by testing SmartConsole login and monitoring process memory.
Caveat Review Check Point release notes for r82.x for any SmartConsole UI or workflow changes that may affect administrative procedures

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

Fix this in Smartconsole Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24915 — 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-24915 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