Cisco Identity Services Engine Software: Missing Authorization
CVE-2025-20125 is a high-severity missing authorization vulnerability in Cisco Identity Services Engine Software from Cisco, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected Cisco Identity Services Engine Software versions: 3.0.0; 3.0.0 p1; 3.0.0 p2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 16.4% chance of exploitation within 30 days, which is in the top 2.98% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Identity Services Engine to 3.1 or a later version.
- Read the advisory on sec.cloudapps.cisco.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Cisco | Cisco Identity Services Engine Software | 3.0.0; 3.0.0 p1; 3.0.0 p2; 3.0.0 p3; 3.1.0; 3.0.0 p4; 3.1.0 p1; 3.0.0 p5; and 23 more ranges | Not stated |
| Cisco | Cisco ISE Passive Identity Connector | 3.0.0; 3.2.0; 3.1.0; 3.3.0 | Not stated |
| Cisco | Identity Services Engine | before 3.1; 3.1.0; 3.2.0; 3.3.0 | 3.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | CNA (cisco.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
A vulnerability in an API of Cisco ISE could allow an authenticated, remote attacker with valid read-only credentials to obtain sensitive information, change node configurations, and restart the node. This vulnerability is due to a lack of authorization in a specific API and improper validation of user-supplied data. An attacker could exploit this vulnerability by sending a crafted HTTP request to a specific API on the device. A successful exploit could allow the attacker to attacker to obtain information, modify system configuration, and reload the device. Note: To successfully exploit this vulnerability, the attacker must have valid read-only administrative credentials. In a single-node deployment, new devices will not be able to authenticate during the reload time.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Cisco Identity Services Engine Software
- 10.0 Critical severity
- 7.6 High severity
- 7.2 High severity
- 8.6 High severity
- 7.1 High severity
- 9.1 Critical severity
Recent Missing Authorization vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
- 9.8 Critical severity
Spotted an error? Tell us.