CVE-2024-24919
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 · uneditedPotentially 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.
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 confidenceAn information disclosure vulnerability in Check Point Security Gateways that allows attackers to read certain sensitive information when the gateway is internet-facing with Remote Access VPN or Mobile Access Software Blades enabled.
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= r80.40= r81= r81.10= r80.20= r80.40= r81.20= r81.10= r81= r80.40= r81= r81.10= r81.20CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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.
-
Identify your Check Point product familyDetermine if the gateway is Quantum Spark, Quantum Security Gateway, or Cloudguard Network SecurityAffected if The product is any of these three families and matches version criteria
-
Check the installed firmware versionUse the gateway's management interface or command line to retrieve the firmware versionAffected if The version is r80.40, r80.20, r81, r81.10, or r81.20
-
Verify if Remote Access VPN is enabledInspect the gateway configuration to determine if the Remote Access VPN Software Blade is activeAffected if Remote Access VPN is enabled on an affected version
-
Verify if Mobile Access Software Blade is enabledInspect the gateway configuration to determine if the Mobile Access Software Blade is activeAffected if Mobile Access is enabled on an affected version
-
Look for signs of unauthorized information accessReview gateway logs and audit records for anomalous requests to sensitive endpoints or filesAffected if Unexplained access to sensitive gateway information is observed in logs after the disclosure date
A user is affected if they run an affected firmware version (r80.40, r80.20, r81, r81.10, or r81.20) on Quantum Spark, Quantum Security Gateway, or Cloudguard Network Security with either Remote Access VPN or Mobile Access Software Blade enabled.
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.
From vendor dataApply the available Check Point security patch to affected gateways. Until patched, ensure vulnerable blades are not exposed directly to the internet or implement additional network segmentation controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24919 — 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-2024-24919 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