CVE-2025-8304
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 · uneditedAn authenticated local user can obtain information that allows claiming security policy rules of another user due to sensitive information being accessible in the Windows Registry keys for Check Point Identity Agent running on a Terminal Server.
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 confidenceCheck Point Identity Agent stores sensitive security policy information in Windows Registry keys accessible to authenticated local users on Terminal Servers. This allows a local authenticated attacker to read registry keys containing credentials or policy data that can be used to impersonate another user and claim their security policy rules.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Check Point Identity Agent is installedOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Check Point\IA (or HKLM\SOFTWARE\Wow6432Node\Check Point\IA if running 32-bit agent on 64-bit system). Alternatively, check for the service named 'CheckpointIA' or 'Check Point Identity Agent' in Services.msc.Affected if The registry key exists or the service is present, indicating Check Point Identity Agent is installed.
-
Identify registry keys containing security policy dataExamine all subkeys under HKLM\SOFTWARE\Check Point\IA (and HKLM\SOFTWARE\Wow6432Node\Check Point\IA). Look for keys with names suggesting sensitive data such as 'Credentials', 'Policy', 'Users', 'Rules', 'Auth', or similar.Affected if Registry keys containing security policy, credentials, or user impersonation data are present under the Check Point Identity Agent registry location.
-
Check registry key ACL permissionsRight-click each identified sensitive registry key in Regedit, select Permissions, then click Advanced. Verify which users and groups have access. Specifically check if 'Authenticated Users' or 'Users' group has any permissions beyond 'Special' or 'Deny'.Affected if Authenticated Users or Users group has Read or Full Control permissions on sensitive registry keys containing policy or credential data.
-
Verify terminal server contextCheck if the Windows server is configured as a Terminal Server (Remote Desktop Services) by opening System Properties (sysdm.cpl) > Remote tab, or by checking if multiple users can log on simultaneously via Remote Desktop.Affected if The system is configured as a Terminal Server or allows multiple concurrent remote desktop sessions, allowing local authenticated attackers to access the vulnerable registry keys.
A user is affected if Check Point Identity Agent is installed on a Terminal Server and its sensitive registry keys containing credentials or policy data are readable by authenticated local users due to permissive ACLs.
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 dataConfigure proper Windows Registry ACLs to restrict access to Check Point Identity Agent registry keys to only privileged accounts, or apply vendor-provided patches if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8304 — 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-2025-8304 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