What is the CVSS score of CVE-2024-38657?

CVE-2024-38657 has a CVSS 3.1 base score of 4.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N. EPSS exploitation probability: 0.6%.

Which versions of Connect Secure are affected by CVE-2024-38657?

Organizations using Ivanti Connect Secure should be aware of moderate risk from CVE-2024-38657 rated CVSS 4.9. Exploitation could compromise the security of affected deployments.

How to fix or mitigate CVE-2024-38657?

Within 30 days: Identify affected systems running Ivanti Connect Secure and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Connect Secure CVE-2024-38657

MEDIUM

External Control of File Name or Path (CWE-73)

2025-02-21 support@hackerone.com

Information Disclosure Ivanti Connect Secure Policy Secure

4.9

CVSS 3.1

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:27 vuln.today

CVE Published

Feb 21, 2025 - 02:15 nvd

MEDIUM 4.9

DescriptionNVD

AnalysisAI

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. Rated medium severity (CVSS 4.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-73. 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. Affected products include: Ivanti Connect Secure, Ivanti Policy Secure. Version information: version 22.7.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.