At the time of publication, this vulnerability affected the following Cisco products if they were running a vulnerable release of Cisco IOS XE Wireless Controller Software and had lobby ambassador user accounts enabled:
- Catalyst 9800-CL Wireless Controllers for Cloud
- Catalyst 9800 Embedded Wireless Controllers for Catalyst 9300, 9400, and 9500 Series Switches
- Catalyst 9800 Series Wireless Controllers
- Embedded Wireless Controllers on Catalyst Access Points
For information about which Cisco software releases were vulnerable at the time of publication, see the Fixed Software section of this advisory.
Determine the Device Configuration
To determine whether a lobby ambassador account and the HTTP server feature are configured on a device, use the following instructions.
Determine the Lobby Ambassador Account Configuration
To determine how many lobby ambassador accounts are configured on a device, log in to the device and run the show running-config | count type lobby-admin CLI command. The following example shows the CLI output on a device with one lobby ambassador account configured:
Router#show running-config | count type lobby-admin
Number of lines which match regexp = 1
The number at the end of the line indicates how many lobby ambassador accounts are configured on the device.
Note: The lobby ambassador role can be associated with a user account that is using RADIUS or TACACS+. Customers who are using an authentication, authorization, and accounting (AAA) server such as Cisco Identity Services Engine (ISE) to manage user accounts that are accessing their device should check for the presence of users that have the cisco-av-pair=lobby-admin attribute set. For an example of how to configure a lobby ambassador account on Cisco ISE, see Configure 9800 WLC Lobby Ambassador with RADIUS and TACACS+ Authentication.
Determine the HTTP Server Configuration
To determine whether the HTTP Server feature is enabled for a device, log in to the device and use the show running-config | include ip http server|secure|active command in the CLI to check for the presence of the ip http server command or the ip http secure-server command in the global configuration. If either command is present, the HTTP Server feature is enabled for the device.
The following example shows the output of the show running-config | include ip http server|secure|active command for a device that has the HTTP Server feature enabled:
Router# show running-config | include ip http server|secure|active
ip http server
ip http secure-server
Note: The presence of either command or both commands in the device configuration indicates that the web UI feature is enabled.
If the ip http server command is present and the configuration also contains ip http active-session-modules none, the vulnerability is not exploitable over HTTP.
If the ip http secure-server command is present and the configuration also contains ip http secure-active-session-modules none, the vulnerability is not exploitable over HTTPS.
Cisco IOS XE Wireless Controller Software is affected by this vulnerability only if the device is configured with a lobby ambassador account. This is not a default configuration and must be added by an administrator.
