Cleartext storage of information in Ivanti Connect Secure before version 22.7R2.6 and Ivanti Policy Secure before version 22.7R1.3 allows a local authenticated attacker with admin privileges to read sensitive data.
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Connect_secure | Ivanti | * | 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) |
| Policy_secure | Ivanti | * | 22.7 (including) |
| Policy_secure | Ivanti | 22.7-r1 (including) | 22.7-r1 (including) |
| Policy_secure | Ivanti | 22.7-r1.1 (including) | 22.7-r1.1 (including) |
| Policy_secure | Ivanti | 22.7-r1.2 (including) | 22.7-r1.2 (including) |
Because the information is stored in cleartext (i.e., unencrypted), attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information. When organizations adopt cloud services, it can be easier for attackers to access the data from anywhere on the Internet. In some systems/environments such as cloud, the use of “double encryption” (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.