A vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to access sensitive information. This vulnerability is due to the improper storage of sensitive information within the web-based management interface. An attacker could exploit this vulnerability by logging in to the web-based management interface and viewing hidden fields within the application. A successful exploit could allow the attacker to access sensitive information, including device entry credentials, that could aid the attacker in further attacks.
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Identity_services_engine | Cisco | * | 2.6.0 (including) |
| Identity_services_engine | Cisco | 2.7.0 (including) | 2.7.0 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch1 (including) | 2.7.0-patch1 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch2 (including) | 2.7.0-patch2 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch3 (including) | 2.7.0-patch3 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch4 (including) | 2.7.0-patch4 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch5 (including) | 2.7.0-patch5 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch6 (including) | 2.7.0-patch6 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch7 (including) | 2.7.0-patch7 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch8 (including) | 2.7.0-patch8 (including) |
| Identity_services_engine | Cisco | 2.7.0-patch9 (including) | 2.7.0-patch9 (including) |
| Identity_services_engine | Cisco | 3.0.0 (including) | 3.0.0 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch1 (including) | 3.0.0-patch1 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch2 (including) | 3.0.0-patch2 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch3 (including) | 3.0.0-patch3 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch4 (including) | 3.0.0-patch4 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch5 (including) | 3.0.0-patch5 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch6 (including) | 3.0.0-patch6 (including) |
| Identity_services_engine | Cisco | 3.0.0-patch7 (including) | 3.0.0-patch7 (including) |
| Identity_services_engine | Cisco | 3.1 (including) | 3.1 (including) |
| Identity_services_engine | Cisco | 3.1-patch1 (including) | 3.1-patch1 (including) |
| Identity_services_engine | Cisco | 3.1-patch3 (including) | 3.1-patch3 (including) |
| Identity_services_engine | Cisco | 3.1-patch4 (including) | 3.1-patch4 (including) |
| Identity_services_engine | Cisco | 3.1-patch5 (including) | 3.1-patch5 (including) |
| Identity_services_engine | Cisco | 3.1-patch6 (including) | 3.1-patch6 (including) |
Network-based products, such as web applications, often run on top of an operating system or similar environment. When the product communicates with outside parties, details about the underlying system are expected to remain hidden, such as path names for data files, other OS users, installed packages, the application environment, etc. This system information may be provided by the product itself, or buried within diagnostic or debugging messages. Debugging information helps an adversary learn about the system and form an attack plan. An information exposure occurs when system data or debugging information leaves the program through an output stream or logging function that makes it accessible to unauthorized parties. Using other weaknesses, an attacker could cause errors to occur; the response to these errors can reveal detailed system information, along with other impacts. An attacker can use messages that reveal technologies, operating systems, and product versions to tune the attack against known vulnerabilities in these technologies. A product may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism.