Who is affected
Cisco Expressway Series devices are vulnerable to exploitation via hard-coded credentials in the database service. An unauthenticated attacker with network access and persistent cookies can execute commands as root on clustered devices. The record does not specify which versions of Expressway Series are affected, nor does it indicate whether on-premises and cloud deployments are equally exposed.
How to check whether this touches you
- Inventory your infrastructure for any Cisco Expressway Series deployments, including those in clustered configurations.
- Confirm whether your Expressway Series instances are reachable from outside your network or are internet-facing; test network-level access to the database service port from untrusted sources.
- Obtain the running software version from the device's administration interface or logs, and cross-reference it against Cisco's advisory; note that version alone is not conclusive if backports have been applied.
- Examine access logs for the database service to establish a baseline of normal client behaviour and any anomalies.
What to do
- Contact Cisco support immediately to obtain the specific patched versions applicable to your Expressway Series instances and the timeline for availability.
- If patching is not immediately available, restrict network access to the Expressway Series database service to trusted internal networks only, using firewall rules or network segmentation.
- Enable persistent logging of all database service connections and authentication attempts; ensure logs are retained for at least 90 days and stored off-device.
- If the device is clustered, audit all nodes for consistent configuration and access controls.
- Apply patches as soon as Cisco releases them, in accordance with CISA's BOD 26-04 risk-based prioritisation guidance.
- If mitigations cannot be implemented and patching is delayed indefinitely, evaluate discontinuation of the product as outlined in the required action.
If you find you were exposed
Exploitation of hard-coded credentials often precedes disclosure; review your logs from the past six months for database service access from unexpected sources or commands executed as root. Cross-reference any suspicious activity with your change logs and security events. If log retention is shorter than six months, document the gap and prioritise retention extension for future incidents. Any evidence of compromise should trigger a forensics triage review in line with CISA's guidance.