CVE-2024-38657 in the critical feed json
External control of a file name in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a…
published 2025-02-21 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-4556
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
External control of a file name in Ivanti Connect Secure before version 22.7R2.4 and Ivanti Policy Secure before version 22.7R1.3 allows a remote authenticated attacker with admin privileges to write arbitrary files.
Patch / fix
- ivanti connect_secure 22.7r2.4
- ivanti policy_secure 22.7r1.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-25-043-01 updated cvss 9.1
Ivanti Connect Secure and Ivanti Policy Secure external file control vulnerability
-
Ivanti Connect Secure <22.7R2.4 Ivanti Policy Secure <22.7R1.3affected: vendor fix forums.ivanti.com
-
Ivanti Connect Secure 22.7R2.4 Ivanti Policy Secure 22.7R1.3fixed: vendor fix forums.ivanti.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 20 mo ago
Exploit prediction
1.62% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Ivanti Connect Secure
- Ivanti Policy Secure
Classification
- Weakness
-
- CWE-73 External Control of File Name or Path
- Technology feeds
References
Sources
- CVE List CVE-2024-38657
- NVD CVE-2024-38657
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.