This vulnerability allows a remote, unauthenticated attacker to create an account on an affected system with privilege level 15 access. The attacker can then use that account to gain control of the affected system.
This vulnerability affects Cisco IOS XE Software if the web UI feature is enabled. The web UI feature ends up enabled through the ip http server or ip http secure-server commands.
To determine whether the HTTP Server feature is enabled for a system, log in to the system 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, according to the advisory. If either command is present, the HTTP Server feature is enabled for the system.
The following example shows the output of the show running-config | include ip http server|secure|active command for a system that has the HTTP Server feature enabled:
Router# show running-config | include ip http server|secure|active
ip http server
ip http secure-server
One note is the presence of either command or both commands in the system configuration indicates 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.
The web UI is an embedded GUI-based system-management tool that provides the ability to provision the system, to simplify system deployment and manageability, and to enhance the user experience. It comes with the default image, so there is no need to enable anything or install any license on the system. The web UI can end up used to build configurations as well as to monitor and troubleshoot the system without CLI expertise.
The web UI and management services should not end up exposed to the Internet or to untrusted networks.
To determine whether a system may have been compromised, perform the following checks:
Check the system logs for the presence of any of the following log messages where user could be cisco_tac_admin, cisco_support or any configured, local user unknown to the network administrator:
%SYS-5-CONFIG_P: Configured programmatically by process SEP_webui_wsma_http from console as user on line
%SEC_LOGIN-5-WEBLOGIN_SUCCESS: Login Success [user: user] [Source: source_IP_address] at 03:42:13 UTC Wed Oct 11 2023
The %SYS-5-CONFIG_P message will be present for each instance a user has accessed the web UI. The indicator to look for is new or unknown usernames present in the message.
Check the system logs for the following message where filename is an unknown filename that does not correlate with an expected file installation action:
%WEBUI-6-INSTALL_OPERATION_INFO: User: username, Install Operation: ADD filename
Cisco Talos provided the following command to check for the presence of the implant where systemip is the IP address of the system to check. This command should be issued from a workstation with access to the system in question:
curl -k -X POST “https://systemip/webui/logoutconfirm.html?logon_hash=1”
If the request returns a hexadecimal string, the implant is present.
If the system is configured for HTTP access only, use the HTTP scheme in the command example.
There are no workarounds that address this vulnerability.
Cisco recommends customers disable the HTTP Server feature on all Internet-facing systems. To disable the HTTP Server feature, use the no ip http server or no ip http secure-server command in global configuration mode. If the HTTP server and HTTPS server are in use, both commands are required to disable the HTTP Server feature.
After disabling the HTTP Server feature, use the copy running-configuration startup-configuration command to save the running-configuration. This will ensure the HTTP Server feature is not unexpectedly enabled in the event of a system reload.

