CVE-2024-52887
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 · uneditedAuthenticated end-user may set a specially crafted SNX bookmark that can make their browser run a script while accessing their own bookmark list.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Check Point SNX (VPN client). An authenticated user can create a malicious bookmark containing JavaScript that executes when the user accesses their own bookmark list. This is a self-XSS where the attacker and victim are the same user.
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 dataall versionsall versionsCVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm Check Point SNX/VPN product is in useIdentify Check Point SNX client or Check Point Mobile Access/Remote Access VPN web portal. Look for snx processes, cpsnxd service, or access to /snx or /RemoteAccess login pages.Affected if The environment uses Check Point SNX, Mobile Access, or Remote Access VPN software.
-
Verify bookmark management feature existsLog into the SNX VPN client or Mobile Access portal as an authenticated user. Navigate to bookmark management or saved connections interface where users can create/edit saved VPN connection entries.Affected if The product provides a bookmark or saved connection feature that allows authenticated users to create custom entries.
-
Test for input sanitization on bookmark fieldsAs an authenticated user, attempt to create a bookmark with a simple script tag in the name or URL field (e.g., <script>alert(1)</script>). Save the bookmark and then access the bookmark list. Observe if the script executes or is rendered as plain text.Affected if User-supplied content in bookmark name/URL fields is reflected back without sanitization or encoding, and the script executes in the browser.
-
Check for Content Security Policy headersUsing browser developer tools or a proxy, capture HTTP responses from the SNX/VPN portal. Inspect response headers for Content-Security-Policy or X-Content-Security-Policy headers.Affected if CSP headers are absent or do not include appropriate directives (like 'script-src') to prevent inline script execution.
-
Confirm attack requires authenticationVerify that the bookmark creation feature is only accessible after successful authentication to the VPN portal, confirming this is a self-XSS requiring authenticated user context.Affected if The vulnerable bookmark feature is only available to authenticated users, meaning the attacker and victim are the same authenticated user.
A user is affected if their environment runs Check Point SNX, Mobile Access, or Remote Access VPN with a bookmark/saved connection feature that allows authenticated users to input custom content that is later rendered without sanitization, enabling stored XSS execution when the user views their bookmarks.
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 vendor patch when available. Implement proper input sanitization and encoding for bookmark names/URLs. Consider implementing Content Security Policy (CSP) headers to mitigate XSS risks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52887 — 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-52887 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