A vulnerability in the web-based management interface of Cisco Identity Services Engine could allow an authenticated, remote attacker to take privileges actions within the web-based management interface. This vulnerability is due to improper access control on a feature within the web-based management interface of the affected system. An attacker could exploit this vulnerability by accessing features through direct requests, bypassing checks within the application. A successful exploit could allow the attacker to take privileged actions within the web-based management interface that should be otherwise restricted.
{{value}} [%7b%7bvalue%7d%7d])}]]
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Identity_services_engine | Cisco | * | 2.6.0 (excluding) |
| Identity_services_engine | Cisco | 2.6.0 (including) | 2.6.0 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch1 (including) | 2.6.0-patch1 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch10 (including) | 2.6.0-patch10 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch11 (including) | 2.6.0-patch11 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch12 (including) | 2.6.0-patch12 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch2 (including) | 2.6.0-patch2 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch3 (including) | 2.6.0-patch3 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch5 (including) | 2.6.0-patch5 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch6 (including) | 2.6.0-patch6 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch7 (including) | 2.6.0-patch7 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch8 (including) | 2.6.0-patch8 (including) |
| Identity_services_engine | Cisco | 2.6.0-patch9 (including) | 2.6.0-patch9 (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 | 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.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.2 (including) | 3.2 (including) |
When a product contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to:
If the caller of the API does not follow these requirements, then it may allow a malicious user or process to elevate their privilege, hijack the process, or steal sensitive data. For instance, it is important to know if privileged APIs do not shed their privileges before returning to the caller or if the privileged function might make certain assumptions about the data, context or state information passed to it by the caller. It is important to always know when and how privileged APIs can be called in order to ensure that their elevated level of privilege cannot be exploited.