Article Details

Original Article Text

Click to Toggle View

Cisco warns that Unified CM has hardcoded root SSH credentials. Cisco has removed a backdoor account from its Unified Communications Manager (Unified CM), which would have allowed remote attackers to log in to unpatched devices with root privileges. Cisco Unified Communications Manager (CUCM), formerly known as Cisco CallManager, serves as the central control system for Cisco's IP telephony systems, handling call routing, device management, and telephony features. The vulnerability (tracked as CVE-2025-20309) was rated as maximum severity, and it is caused by static user credentials for the root account, which were intended for use during development and testing. According to a Cisco security advisory released on Wednesday, CVE-2025-20309 affects Cisco Unified CM and Unified CM SME Engineering Special (ES) releases 15.0.1.13010-1 through 15.0.1.13017-1, regardless of the device configuration. The company added that there are no workarounds that address the vulnerability. Admins can only fix the flaw and remove the backdoor account by upgrading vulnerable devices to Cisco Unified CM and Unified CM SME 15SU3 (July 2025) or by applying the CSCwp27755 patch file available here. "A vulnerability in Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) could allow an unauthenticated, remote attacker to log in to an affected device using the root account, which has default, static credentials that cannot be changed or deleted," Cisco explained. Following successful exploitation, attackers could gain access to the vulnerable systems and execute arbitrary commands with root privileges. While the Cisco Product Security Incident Response Team (PSIRT) is not yet aware of proof-of-concept code available online or exploitation in attacks, the company has released indicators of compromise to help identify impacted devices. As Cisco stated, exploitation of CVE-2025-20309 would result in a log entry to /var/log/active/syslog/secure for the root user with root permissions. Since logging of this event is enabled by default, admins can retrieve the logs to look for exploitation attempts by running the following command from the command line: file get activelog syslog/secure. This is far from the first backdoor account Cisco had to remove from its products in recent years, with previous hardcoded credentials found in its IOS XE, Wide Area Application Services (WAAS), Digital Network Architecture (DNA) Center, and Emergency Responder software. More recently, Cisco warned admins in April to patch a critical Cisco Smart Licensing Utility (CSLU) vulnerability that exposes a built-in backdoor admin account used in attacks. One month later, the company removed a hardcoded JSON Web Token (JWT) that allows unauthenticated remote attackers to take over IOS XE devices. 8 Common Threats in 2025 While cloud attacks may be growing more sophisticated, attackers still succeed with surprisingly simple techniques. Drawing from Wiz's detections across thousands of organizations, this report reveals 8 key techniques used by cloud-fluent threat actors.

Daily Brief Summary

CYBERCRIME // Cisco Removes Hardcoded Credentials from Unified CM

Cisco has issued a security advisory for a severe vulnerability in its Unified Communications Manager.

The flaw, identified as CVE-2025-20309, involves hardcoded root SSH credentials that could enable remote attackers to access devices with root privileges.

Affected versions include Unified CM and Unified CM SME Engineering Special releases from 15.0.1.13010-1 to 15.0.1.13017-1.

There are no alternative workarounds; the vulnerability can only be mitigated by upgrading to newer software versions or applying a specific patch.

Cisco has not detected any active exploitation of this vulnerability but has provided indicators of compromise to help administrators assess their systems.

This incident adds to a list of issues with hardcoded credentials previously discovered in other Cisco products.

The company stressed the importance of monitoring system logs for unauthorized access attempts, with detailed instructions on how to retrieve relevant log entries.