CVE Vulnerabilities

CVE-2025-55147

Cross-Site Request Forgery (CSRF)

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

CSRF 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 unauthenticated attacker to execute sensitive actions on behalf of the victim user. User interaction is required

Weakness

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

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

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]

References