dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2018-15403

MEDIUM · 5.4 CVSS v3.0 Published 2018-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Open redirect vulnerability in Cisco web interfaces (Emergency Responder, Unified Communications Manager, IM & Presence Service, Unity Connection) allows authenticated remote attackers to craft HTTP requests with malicious redirect URLs due to improper input validation of request parameters.

MitigationImplement strict validation of redirect URL parameters to ensure only legitimate, internal redirects are allowed; apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Unified Communications ManagerApplication
Affected:= 10.5\(2.10000.5\)= 11.0\(1.10000.10\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)
Unity ConnectionApplication
Affected:= 9.1\(1\)es23
Unified Communications Manager Im And Presence ServiceApplication
Affected:= 10.5\(1\)= 10.5\(2\)= 12.0\(1\)= 12.5\(1\)
Emergency ResponderApplication
Affected:= 11.5\(4.59000.1\)= 12.0\(1.40000.3\)= 12.5\(0.98000.110\)

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco product
    Access the web interface or check system documentation for the product name (Cisco Unified Communications Manager, Unity Connection, IM & Presence Service, or Emergency Responder)
    Affected if The product is one of the four affected by this CVE
  2. Check product version
    Locate the version number in the web interface footer, about page, or system administration console
    Affected if Version matches one of the specific versions listed: CUCM 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6), 12.0(1.10000.10); Unity Connection 9.1(1)es23; IM&P 10.5(1), 10.5(2), 12.0(1), 12.5(1); Emergency Responder 11.5(4.59000.1), 12.0(1.40000.3), 12.5(0.98000.110)
  3. Verify web interface is accessible
    Confirm the Cisco web interface (HTTPS on port 8443 or 443) is reachable and accepts authentication
    Affected if The web interface is exposed and users can authenticate to it
  4. Inspect redirect parameter handling
    Log into the web interface and observe how the application handles redirect parameters in URLs, particularly after login or when navigating between pages
    Affected if The application accepts and follows redirect URLs in request parameters without proper validation

A user is affected if they run one of the specific product versions listed and have the Cisco web interface accessible and authenticated, allowing redirect URL parameters to be manipulated.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation of redirect URL parameters to ensure only legitimate, internal redirects are allowed; apply vendor patches when available.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15403 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15403 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data