CVE-2025-55144
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 · uneditedMissing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gateway before 2.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote authenticated attacker with read-only admin privileges to configure restricted settings.
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 confidenceThis is an authorization bypass vulnerability where a read-only admin user can configure restricted settings that should only be accessible to higher-privilege administrators. The system fails to properly enforce role-based access controls during configuration operations.
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.7< 22.7= 22.7= 22.8< 22.8= 22.8CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 product versionAccess the admin console and navigate to System > Administration > System Configuration > General, or use the CLI command 'show version' to display the installed software versionAffected if Version is less than 22.7 or equals 22.7 for Connect Secure or Policy Secure; or version equals 22.8 for Zero Trust Access Gateway; or version is less than 22.8 or equals 22.8 for Ivanti Neurons For Secure Access
-
Verify read-only admin role existsIn the admin console, go to Users > Administrative Users > Administrators and review the list of administrative accounts and their assigned rolesAffected if A read-only administrator role is configured in the system
-
Test restricted settings access for read-only adminLog in with a read-only admin account and attempt to access or modify configuration settings that should be restricted to full administrators, such as system settings, authentication servers, or network configurationAffected if Read-only admin can view or modify settings that should require higher privilege level, indicating RBAC enforcement is bypassed
-
Review admin role permissions configurationIn the admin console, go to Users > Administrative Users > Roles and examine the permissions assigned to each role, specifically checking if read-only role has unintended write access to restricted configuration areasAffected if Read-only role has been granted write or modify permissions to restricted settings that should only be accessible to full administrators
You are affected if your installed version falls within the affected ranges AND a read-only administrator can modify settings that should be restricted to higher-privilege admins, indicating the RBAC bypass is present.
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.722.8
Apply the vendor-provided patches (22.7R2.9, 22.8R2, 22.7R1.6, 2.8R2.3-723, or 22.8R1.4 depending on product) and verify that read-only admin accounts can no longer modify restricted settings.
Upgrade to product-specific fixed release: Connect Secure 22.7R2.9/22.8R2, Policy Secure 22.7R1.6, ZTA Gateway 2.8R2.3-723, Neurons for Secure Access 22.8R1.4
- 1. Identify the specific Ivanti product running (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access)
- 2. Check the current installed version of the affected product
- 3. For Connect Secure: upgrade to version 22.7R2.9 or 22.8R2
- 4. For Policy Secure: upgrade to version 22.7R1.6
- 5. For Zero Trust Access Gateway: upgrade to version 2.8R2.3-723
- 6. For Neurons for Secure Access: upgrade to version 22.8R1.4
- 7. After upgrade, verify the fix was applied by confirming the version matches the fixed release
- 8. Test that read-only admin accounts can no longer modify restricted settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55144 — 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-55144 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