CriticalCVE-2024-24919

    Information disclosure (CVE-2024-24919)

    Published In CISA KEV since Sources: CVE.org, SingCERT, NCSC NZ, pwn.watch

    What is affected, what to do

    Potentially allowing an attacker to read certain information on Check Point Security Gateways once connected to the internet and enabled with remote Access VPN or Mobile Access Software Blades. A Security fix that mitigates this vulnerability is available.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Check Point Quantum Gateway, Spark Gateway and CloudGuard Network eq Check Point Quantum Gateway and CloudGuard Network versions R81.20, R81.10, R81, R80.40 and Check Point Spark versions R81.10, R..Check Point Quantum Gateway and CloudGuard Network versions R81.20, R81.10, R81, R80.40 and Check Point Spark versions R81.10, R

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.6

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.6

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, SingCERT, NCSC NZ, pwn.watch

    99.98 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.98

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    253.28 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: ANSSI / CERT-FR, NCSC NZ, CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.6 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.6
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.98 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.98
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-200

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because it is unauthenticated, network-reachable and requires no user interaction — a single HTTP request is enough to read sensitive files, including password hashes, from the gateway. Its exploitation likelihood is among the highest in the entire KEV catalogue, CISA confirms use by ransomware operators, and credentials harvested from compromised gateways are routinely resold as initial-access vectors into AD environments. The target profile is any organisation running an internet-facing Check Point perimeter with Remote Access enabled; for NIS2 and KRITIS scope this is a crown-jewel perimeter asset, so the patch SLA should be no more than 24 h, paired with mandatory credential rotation — without rotation the risk persists even after patching.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the Check Point vendor hotfix immediately. Affected products are Quantum Security Gateway, Quantum Spark, Quantum Maestro/Scalable Chassis and CloudGuard Network Security with the IPsec VPN, Mobile Access or Remote Access VPN blade enabled. Pull the fix and sk article (sk182336) from the Check Point User Center and roll it out across all affected gateways — no reboot required.
      • If an immediate patch window is impossible, temporarily disable the Mobile Access blade and Remote Access VPN on internet-facing gateways, or restrict access to the SSL VPN portals (TCP/443) to known source IP ranges via policy.
      • Rotate every local account on the gateway, especially admin and any locally stored service accounts. Also rotate LDAP/RADIUS bind credentials cached on the gateway — the flaw lets an attacker read password hashes and config files.
      • Reissue certificates and pre-shared keys for site-to-site VPN tunnels, since /etc/shadow hashes and VPN key material may have been exfiltrated.
      • Hunt for indicators across the last 90 days: look for ../ traversal against /clients/MyCRL and anomalous POSTs to cgi-bin paths (see detection section). On any hit, trigger IR and image the gateway before patching.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: never expose the management interface (TCP/257, TCP/18190, TCP/18264) to the internet; reach it only via admin VLAN or jump host.
      • Perimeter WAF or reverse proxy in front of the Mobile Access portal: block requests containing path-traversal patterns (..%2f, ..%5c, encoded dot sequences); apply rate-limiting on login and CRL endpoints.
      • Enforce MFA for every Remote Access VPN user; disable local password accounts on the gateway and authenticate only via certificates or SAML/RADIUS with MFA.
      • Activate the Check Point IPS signature "Check Point VPN Information Disclosure (CVE-2024-24919)" in Prevent mode; refresh the equivalent Suricata/Snort rulesets (ET WEB_SPECIFIC_APPS Check Point) on perimeter IDS.
      • Egress filtering on the gateway itself: allow outbound connections from management processes only to defined update and logging targets; block egress to Tor exits and bulk VPS providers to contain post-exploitation exfiltration.
      • Configuration review: $FWDIR/conf/, /etc/shadow and /etc/CPshrd-R81/registry/HKLM_registry.data are the typical target files — audit file permissions and disable unused blades (DLP, URL filtering with credential stores) that increase the readable attack surface.

    3. Runbook step 3

      Detection rules

      • Mobile Access/SSL VPN portal web access logs: GET/POST requests containing aCSHELL/../../../, /clients/MyCRL or encoded traversal (%2e%2e%2f). Sigma shape: selection: cs-uri-stem|contains: ['/clients/MyCRL','aCSHELL/..'].
      • Zeek/Suricata http.log: unexpectedly large response bodies (> 10 KB) on CRL endpoints, or response Content-Type text/plain instead of application/pkix-crl.
      • Gateway audit logs (/var/log/messages, fw.log): reads against /etc/shadow or fwauth.NDB outside scheduled backup windows; cpshell sessions without a preceding successful SSH login.
      • EDR/XDR on jump hosts and admin workstations: pass-the-hash or Kerberoasting activity against AD appearing shortly after portal access, especially using credentials previously only present in the gateway LDAP bind config.
      • SIEM correlation: repeated HTTP 200 responses to anomalous URI paths from a single source IP at short intervals (< 2 s) indicate mass enumeration. KQL shape: W3CIISLog | where csUriStem has_any ("MyCRL","aCSHELL") | summarize count() by cIP, bin(TimeGenerated,5m) | where count_ > 20.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Potentially allowing an attacker to read certain information on Check Point Security Gateways once connected to the internet and enabled with remote Access VPN or Mobile Access Software Blades. A Security fix that mitigates this vulnerability is available.

    Source: cvelistv5, CSA/SingCERT, NCSC NZ (CC BY 4.0), pwn.watch, CISA KEV Catalog, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    checkpointCheck Point Quantum Gateway, Spark Gateway and CloudGuard Network
    • Check Point Quantum Gateway and CloudGuard Network versions R81.20, R81.10, R81, R80.40 and Check Point Spark versions R81.10, R
    • —
    checkpointcloudguard_network_security
    • r80.40
    • r81.20
    • r81
    • r81.10
    • —
    • —
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Othercheckpointquantum_security_gateway_firmwarer80.40
    Othercheckpointquantum_security_gateway_firmwarer81
    Othercheckpointquantum_security_gateway_firmwarer81.10
    Othercheckpointquantum_security_gateway_firmwarer81.20
    Othercheckpointquantum_spark_firmwarer80.20
    Othercheckpointquantum_spark_firmwarer80.40
    Othercheckpointquantum_spark_firmwarer81
    Othercheckpointquantum_spark_firmwarer81.10

    Weakness classes (CWE)

    • CWE-200Exposure of Sensitive Information to an Unauthorized Actor

      Class

      The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

      Entry at MITRE CWE-200

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of High-Severity Vulnerability in Check Point Virtual Private Network (VPN) Products (opens in a new tab)CSA/SingCERTactively exploited
    NCSC NZCVE affecting Check Point Security Gateway (opens in a new tab)NCSC NZactively exploited
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2024-ALE-008 – [MàJ] Vulnérabilité dans les produits Check Point (clôturée 2024-07-01) (opens in a new tab)cert.cyber.gouv.fractively exploited
    PoC-in-GitHub (nomi-sec)Incident-Analysis-Response-Check-Point-Security-Gateway-CVE-2024-24919-LFI-Exploitation (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • support.checkpoint.comCheck Point sk182336: preventative hotfix for CVE-2024-24919pwn-watch
    • mnemonic.ioresources/blog/advisory-check-point-remote-access-vpn-vulnerabi…Exploit
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-24919government-resource
    • cert.atCERT.at: Update #1: Sicherheitslücke in Check Point Network Security Gateways (Mobile Access) - Fix verfügbarcert-at
    • cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2024-ALE-008 – [MàJ] Vulnérabilité dans les produits Check Point (clôturée 2024-07-01)cert-fr
    • pwn.watchpwn.watch: Check Point VPN gateway arbitrary file read (CVE-2024-24919) exploitedpwn-watch
    • labs.watchtowr.comCheck Point - Wrong Check Point (CVE-2024-24919)pwn-watch
    • NVD (NIST)NVD: CVE-2024-24919pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-24919
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-24919"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-24919.svg?lang=en" alt="CVE-2024-24919 – NEOSEC Intel" height="20"></a>