cve.bz

CVE-2024-24916 checkpoint smartconsole: Uncontrolled Search Path Element

7.8 highEPSS 2.8%

High (7.8) in checkpoint smartconsole. EPSS 2.8% estimated probability of exploitation activity in the next 30 days.

On this page
Untrusted DLLs in the installer's directory may be loaded and executed, leading to potentially arbitrary code execution with the installer's privileges (admin).

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
2.8% (unchanged from 2.8% a week ago; 2.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-06-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-427 Uncontrolled Search Path Element
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-24916 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-24916?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-24916?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-24916 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
checkpoint:smartconsoler81.10:build400
checkpoint:smartconsoler81.10:build402
checkpoint:smartconsoler81.10:build404
checkpoint:smartconsoler81.10:build406
checkpoint:smartconsoler81.10:build407
checkpoint:smartconsoler81.10:build409
checkpoint:smartconsoler81.10:build410
checkpoint:smartconsoler81.10:build412
checkpoint:smartconsoler81.10:build413
checkpoint:smartconsoler81.10:build414
checkpoint:smartconsoler81.10:build416
checkpoint:smartconsoler81.10:build417
checkpoint:smartconsoler81.10:build418
checkpoint:smartconsoler81.10:build420
checkpoint:smartconsoler81.10:build423
checkpoint:smartconsoler81.10:build424
checkpoint:smartconsoler81.10:build425
checkpoint:smartconsoler81.20:build640
checkpoint:smartconsoler81.20:build641
checkpoint:smartconsoler81.20:build645
checkpoint:smartconsoler81.20:build646
checkpoint:smartconsoler81.20:build649
checkpoint:smartconsoler81.20:build651
checkpoint:smartconsoler81.20:build653
checkpoint:smartconsoler81.20:build654
checkpoint:smartconsoler81.20:build655

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
  • CAPEC-471 Search Order Hijacking Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON