Ivanti Connect Secure/Policy Secure up to 22.7R2.0 argument injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Ivanti Connect Secure and Policy Secure up to 22.7R2.0. This impacts an unknown function. This manipulation causes argument injection. This vulnerability appears as CVE-2024-38655. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Ivanti Connect Secure and Policy Secure up to 22.7R2.0. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a argument injection vulnerability. The CWE definition for the vulnerability is CWE-88. The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Argument injection in Ivanti Connect Secure before version 22.7R2.1 and Ivanti Policy Secure before version 22.7R1.1 allows a remote authenticated attacker with admin privileges to achieve remote code execution.
The advisory is shared at forums.ivanti.com. This vulnerability is known as CVE-2024-38655 since 06/19/2024. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 211455 (Pulse Connect Secure < 22.7R2.1 Multiple Vulnerabilities (000096001)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 22.7R2.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (211455). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 7.2
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 9.1
CNA Vector (hackerone): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Argument injectionCWE: CWE-88 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 211455
Nessus Name: Pulse Connect Secure < 22.7R2.1 Multiple Vulnerabilities (000096001)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Connect Secure/Policy Secure 22.7R2.1
Timeline
06/19/2024 🔍11/13/2024 🔍
11/13/2024 🔍
06/28/2025 🔍
Sources
Advisory: forums.ivanti.comStatus: Confirmed
CVE: CVE-2024-38655 (🔍)
GCVE (CVE): GCVE-0-2024-38655
GCVE (VulDB): GCVE-100-284293
Entry
Created: 11/13/2024 08:48Updated: 06/28/2025 03:27
Changes: 11/13/2024 08:48 (63), 11/15/2024 21:27 (2), 11/23/2024 22:46 (1), 06/28/2025 03:27 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.