Information disclosure vulnerability exists in Pgpool-II 4.4.0 to 4.4.1 (4.4 series), 4.3.0 to 4.3.4 (4.3 series), 4.2.0 to 4.2.11 (4.2 series), 4.1.0 to 4.1.14 (4.1 series), 4.0.0 to 4.0.21 (4.0 series), All versions of 3.7 series, All versions of 3.6 series, All versions of 3.5 series, All versions of 3.4 series, and All versions of 3.3 series. A specific database users authentication information may be obtained by another database user. As a result, the information stored in the database may be altered and/or database may be suspended by a remote attacker who successfully logged in the product with the obtained credentials.
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Pgpool-ii | Pgpool | 3.3.0 (including) | 3.7.12 (including) |
| Pgpool-ii | Pgpool | 4.0.0 (including) | 4.0.22 (excluding) |
| Pgpool-ii | Pgpool | 4.1.0 (including) | 4.1.15 (excluding) |
| Pgpool-ii | Pgpool | 4.2.0 (including) | 4.2.12 (excluding) |
| Pgpool-ii | Pgpool | 4.3.0 (including) | 4.3.5 (excluding) |
| Pgpool-ii | Pgpool | 4.4.0 (including) | 4.4.2 (excluding) |
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.