CVE-2025-5464
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 · uneditedInsertion of sensitive information into a log file in Ivanti Connect Secure before version 22.7R2.8 allows a local authenticated attacker to obtain that information.
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 · high confidenceIvanti Connect Secure before version 22.7R2.8 contains a vulnerability where sensitive information is written to log files. A locally authenticated attacker can access these log files to obtain the exposed sensitive data.
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< 22.7= 22.7CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Check Ivanti Connect Secure versionAccess the admin console or run 'ivnti --version' from command line. Alternatively, check the /etc/version file or the system diagnostics export.Affected if The installed version is any version before 22.7R2.8, or exactly version 22.7 (versions < 22.7 or = 22.7)
-
Identify log file locationsCheck the standard log directories such as /var/log/, /var/tmp/, or the logs directory within the Ivanti installation path. Look for files with 'log' extension or common naming patterns like 'system.log', 'audit.log', or 'access.log'.Affected if Log files exist and contain sensitive information such as credentials, session tokens, or API keys in plain text
-
Inspect log file contents for sensitive dataUse 'grep -i' to search log files for patterns like 'password', 'secret', 'token', 'key', 'credential', or 'authorization'. Examine any entries that appear to contain configuration details or authentication parameters.Affected if Plain-text passwords, API keys, session tokens, or other sensitive credentials are found in log files
-
Verify log file permissionsRun 'ls -la' on identified log files to check owner, group, and permission bits. Determine if non-privileged local users have read access (permissions should not include 'r' for 'others').Affected if Log files are readable by non-admin users (permission bits include 'r--' or 'r-x' for 'others' or non-owner users)
-
Check for unauthorized local user accountsReview /etc/passwd or the local user database to identify all locally authenticated user accounts. Determine which users have shell access or file system access.Affected if Multiple local user accounts exist beyond the intended administrator account, increasing the attack surface
You are affected if Ivanti Connect Secure is version 22.7 or any version before 22.7R2.8 AND log files containing sensitive data are readable by local authenticated users.
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.
dbcve · scoped22.7
Upgrade Ivanti Connect Secure to version 22.7R2.8 or later. As a compensating control, restrict local access to the system and review log file permissions.
Ivanti Connect Secure 22.7R2.8 or later
- 1. Identify the current Ivanti Connect Secure version running in your environment
- 2. Review the version against the affected versions: anything below 22.7R2.8 is vulnerable
- 3. Plan an upgrade to version 22.7R2.8 or later following Ivanti's standard upgrade procedures
- 4. Before upgrading, backup the current configuration
- 5. After upgrading, verify the version is 22.7R2.8 or higher
- 6. Review system logs to confirm the fix is active and no sensitive data is being written to logs
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-5464 — 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-5464 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