CVE-2025-8305
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 printed in plaintext in Identity Agent for Terminal Services debug files.
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 an information disclosure vulnerability in Dell Identity Agent for Terminal Services where debug log files contain plaintext sensitive information. An authenticated local user can read these debug files to obtain credentials or session data that allows them to impersonate another user and claim their security policy rules, effectively achieving unauthorized privilege escalation.
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 Dell Identity Agent for Terminal Services is installedCheck for the presence of the Dell Identity Agent application on the system. Look in Program Files for 'Dell Identity Agent' or check Windows Services for 'Dell Identity Agent' service.Affected if The product is installed and running on the system.
-
Locate debug log filesSearch the application installation directory and common log locations (such as %ProgramData%\Dell\IdentityAgent\Logs or similar paths under the installation folder) for log files with 'debug' in the filename or file extension.Affected if Debug log files exist on the system.
-
Check debug log file permissionsReview file system permissions on identified debug log files to determine if standard users or non-privileged accounts have read access. Use icacls or file properties to inspect the Access Control List.Affected if Debug log files are readable by non-admin users.
-
Search debug logs for sensitive stringsOpen or parse the debug log files and search for patterns indicating sensitive data: look for keywords such as 'password', 'credential', 'session', 'token', 'authentication', or base64-encoded strings that may represent credentials.Affected if Debug logs contain plaintext credentials, session tokens, or authentication data.
-
Confirm debug logging is enabled in configurationExamine the application's configuration files (commonly found in the installation directory or %ProgramData%) for settings related to debug logging, trace logging, or verbose logging. Look for parameters like 'DebugLevel', 'EnableDebug', 'LogLevel=Debug', or similar.Affected if Debug or verbose logging is turned on in the configuration.
A user is affected if Dell Identity Agent for Terminal Services is installed with debug logging enabled and its debug log files are accessible to non-privileged users, containing exposed credentials or session data.
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 dataDisable debug logging in production environments or ensure debug files are stored in secure locations with restricted access. Review and rotate any credentials that may have been exposed in debug output.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8305 — 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-8305 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