An issue was discovered in cookie encryption in phpMyAdmin. The decryption of the username/password is vulnerable to a padding oracle attack. This can allow an attacker who has access to a users browser cookie file to decrypt the username and password. Furthermore, the same initialization vector (IV) is used to hash the username and password stored in the phpMyAdmin cookie. If a user has the same password as their username, an attacker who examines the browser cookie can see that they are the same - but the attacker can not directly decode these values from the cookie as it is still hashed. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Phpmyadmin | Phpmyadmin | 4.4.0 (including) | 4.4.0 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.1 (including) | 4.4.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.1.1 (including) | 4.4.1.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.2 (including) | 4.4.2 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.3 (including) | 4.4.3 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.4 (including) | 4.4.4 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.5 (including) | 4.4.5 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.6 (including) | 4.4.6 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.6.1 (including) | 4.4.6.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.7 (including) | 4.4.7 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.8 (including) | 4.4.8 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.9 (including) | 4.4.9 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.10 (including) | 4.4.10 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.11 (including) | 4.4.11 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.12 (including) | 4.4.12 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.13 (including) | 4.4.13 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.13.1 (including) | 4.4.13.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.14 (including) | 4.4.14 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.14.1 (including) | 4.4.14.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15 (including) | 4.4.15 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.1 (including) | 4.4.15.1 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.2 (including) | 4.4.15.2 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.3 (including) | 4.4.15.3 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.4 (including) | 4.4.15.4 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.5 (including) | 4.4.15.5 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.6 (including) | 4.4.15.6 (including) |
| Phpmyadmin | Phpmyadmin | 4.4.15.7 (including) | 4.4.15.7 (including) |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.