CVE intelligence and bounded remediation

CVE-2018-15403 — Cisco Unified Communications Manager security vulnerability

Medium CVSS 5.4

A vulnerability in the web interface of Cisco Emergency Responder, Cisco Unified Communications Manager, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an authenticated, remote attacker to redirect a user to a malicious web page. The vulnerability is due to improper input validation of the parameters of an HTTP request. An attacker could exploit this vulnerability by crafting an HTTP request that causes the web interface to redirect a request to a specific malicious URL. This type of vulnerability is known as an open redirect attack and is used in phishing attacks that get users to unknowingly visit malicious sites.

Severity
Medium
CVSS
5.4 (3.0)
Published
2018-10-05
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-601

Affected products

  • cisco / unified_communications_manager / 10.5(2.10000.5)
  • cisco / unified_communications_manager / 11.0(1.10000.10)
  • cisco / unified_communications_manager / 11.5(1.10000.6)
  • cisco / unified_communications_manager / 12.0(1.10000.10)
  • cisco / unity_connection / 9.1(1)es23
  • cisco / unified_communications_manager_im_and_presence_service / 10.5(1)

Showing 6 representative product identities from 12 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.