Unified Communications ManagerApplication · Cisco

CVE-2013-3404

HIGH · 7.5 CVSS v2.0 Published 2013-07-18

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

SQL injection vulnerability in Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(1a) allows remote attackers to execute arbitrary SQL commands via unspecified vectors, leading to discovery of encrypted credentials by leveraging metadata, aka Bug ID CSCuh01051.

Technical summary

dbcve analysis · high confidence

SQL injection vulnerability in Cisco Unified Communications Manager (CUCM) versions 7.1(x) through 9.1(1a) allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The vulnerability enables discovery of encrypted credentials by leveraging database metadata, providing an attacker with sensitive authentication material.

MitigationUpgrade Cisco Unified Communications Manager to a version beyond 9.1(1a) that addresses this vulnerability. If immediate patching is not possible, restrict network access to the CUCM management interfaces and monitor for suspicious SQL-like patterns in logs.

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

Affected products & versions

NVD · CPE data

Unified Communications ManagerApplication

Affected:= 7.1$2a$= 7.1$2a$su1= 7.1$2b$= 7.1$2b$su1= 7.1$3$= 7.1$3a$= 7.1$3a$su1= 7.1$3a$su1a= 7.1$3b$= 7.1$3b$su1= 7.1$3b$su2= 7.1$5$

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

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

Confirm Cisco Unified Communications Manager is installed

Locate CUCM installation by checking for the 'Cisco Unified Communications Manager' service or product installation directory, typically under /usr/local/cm/ or via the OS service list

Affected if CUCM software is present on the system
Identify the installed CUCM version

Run the CLI command 'show version' from the CUCM server console or access the Cisco Unified Reporting tool to retrieve the exact version number

Affected if The installed version falls within 7.1(2a) through 9.1(1a), including any 7.1.x variants up to 7.1(5) and versions 8.x through 9.1(1a)
Verify management interface accessibility

Check network configuration for CUCM web interface (HTTPS port 8443) and CTI manager port exposure to determine if the interface is reachable from untrusted networks

Affected if CUCM admin interfaces are exposed to networks beyond the trusted internal network
Review logs for suspicious SQL patterns

Examine CUCM SDS and RTMT logs located in /var/log/active/ for SQL injection attempt indicators such as unexpected SQL syntax, UNION SELECT statements, or anomalous database queries

Affected if Logs contain SQL-like patterns or unauthorized database queries originating from external sources

A system is affected if it runs Cisco Unified Communications Manager version 7.1(x) through 9.1(1a) and has its management interfaces network-accessible, as the SQL injection flaw exists in that version range.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Cisco Unified Communications Manager to a version beyond 9.1(1a) that addresses this vulnerability. If immediate patching is not possible, restrict network access to the CUCM management interfaces and monitor for suspicious SQL-like patterns in logs.

Fix this in Unified Communications Manager Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA4.0 h

40.0 hours of engineering $7,000

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2013-3404 — 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

Primary sources

tools.cisco.comVendor Advisory
secunia.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2013-3404?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 1.1%

Affects: Unified Communications Manager

Remediation

A high-priority fix

Fix this in Unified Communications Manager 40 hrs · Moderate

Typical engagement from $7,000

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-3404 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References