CVE Vulnerabilities

CVE-2025-55142

Missing Authorization

Published: Sep 09, 2025 | Modified: Sep 24, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Missing 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 authentication related settings.

Weakness

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Affected Software

Name Vendor Start Version End Version
Connect_secure Ivanti * 22.7 (excluding)
Connect_secure Ivanti 22.7 (including) 22.7 (including)
Connect_secure Ivanti 22.7-r1 (including) 22.7-r1 (including)
Connect_secure Ivanti 22.7-r1.1 (including) 22.7-r1.1 (including)
Connect_secure Ivanti 22.7-r1.2 (including) 22.7-r1.2 (including)
Connect_secure Ivanti 22.7-r1.3 (including) 22.7-r1.3 (including)
Connect_secure Ivanti 22.7-r1.4 (including) 22.7-r1.4 (including)
Connect_secure Ivanti 22.7-r1.5 (including) 22.7-r1.5 (including)
Connect_secure Ivanti 22.7-r2 (including) 22.7-r2 (including)
Connect_secure Ivanti 22.7-r2.1 (including) 22.7-r2.1 (including)
Connect_secure Ivanti 22.7-r2.2 (including) 22.7-r2.2 (including)
Connect_secure Ivanti 22.7-r2.3 (including) 22.7-r2.3 (including)
Connect_secure Ivanti 22.7-r2.4 (including) 22.7-r2.4 (including)
Connect_secure Ivanti 22.7-r2.5 (including) 22.7-r2.5 (including)
Connect_secure Ivanti 22.7-r2.6 (including) 22.7-r2.6 (including)
Connect_secure Ivanti 22.7-r2.7 (including) 22.7-r2.7 (including)
Connect_secure Ivanti 22.7-r2.8 (including) 22.7-r2.8 (including)

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References