Cisco IOS XE Software: Incorrect Authorization
CVE-2024-20510 is a critical-severity incorrect authorization vulnerability in Cisco IOS XE Software from Cisco, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Cisco IOS XE Software versions: 16.3.1; 16.3.2; 16.3.3, 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 0.28% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Cisco IOS XE Software you run against the affected versions below, and install the vendor's latest release.
- 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 IOS XE Software | 16.3.1; 16.3.2; 16.3.3; 16.3.1a; 16.3.4; 16.3.5; 16.3.5b; 16.3.6; and 32 more ranges | Not stated |
| Cisco | iOS Xe | 16.3.1; 16.3.1a; 16.3.2; 16.3.3; 16.3.4; 16.3.5; 16.3.5b; 16.3.6; and 32 more ranges | Not stated |
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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 4.7 | Medium | CNA (cisco.com) |
| CVSS 3.1 | 9.3 | Critical | NVD |
Official description
A vulnerability in the Central Web Authentication (CWA) feature of Cisco IOS XE Software for Wireless Controllers could allow an unauthenticated, adjacent attacker to bypass the pre-authentication access control list (ACL), which could allow access to network resources before user authentication. This vulnerability is due to a logic error when activating the pre-authentication ACL that is received from the authentication, authorization, and accounting (AAA) server. An attacker could exploit this vulnerability by connecting to a wireless network that is configured for CWA and sending traffic through an affected device that should be denied by the configured ACL before user authentication. A successful exploit could allow the attacker to bypass configured ACL protections on the affected device before the user authentication is completed, allowing the attacker to access trusted networks that the device might be protecting.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
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
Advisories
Other vulnerabilities in Cisco IOS XE Software
- 8.6 High severity
- 8.6 High severity
- 9.8 Critical severity
- 8.6 High severity
- 8.6 High severity
- 8.6 High severity
Recent Incorrect Authorization vulnerabilities
- 9.8 Critical severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.1 Critical severity
Spotted an error? Tell us.