Unity ConnectionApplication · Cisco
CVE-2015-6299
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 · uneditedSQL injection vulnerability in the web interface in Cisco Unity Connection 9.1(1.2) and earlier allows remote authenticated users to execute arbitrary SQL commands via a crafted POST request, aka Bug ID CSCuv63824.
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 confidenceSQL injection vulnerability in the Cisco Unity Connection web interface allows authenticated remote attackers to execute arbitrary SQL commands via crafted POST requests. The vulnerability affects version 9.1(1.2) and earlier, requiring valid authentication to exploit.
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
Unity ConnectionApplication
= 9.1\(1\)= 9.1\(2\)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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Unity Connection installationOn the Cisco server, run the command 'show version' in the CLI or check the Cisco Unity Connection admin web interface for product identification.Affected if The product identified is Cisco Unity Connection.
-
Determine installed versionAccess the Cisco Unity Connection admin web interface and navigate to About page, or run 'utils system version' command in the CLI to retrieve the exact version number.Affected if The installed version is 9.1(1), 9.1(1.1), 9.1(1.2), or any version earlier than 9.1(1).
-
Verify web interface accessibilityCheck if the Cisco Unity Connection web interface (HTTPS on port 8443 or 443) is listening and reachable from network locations using 'show webapp session' or by reviewing server network listeners.Affected if The web interface is exposed and accepts authentication requests.
-
Confirm SQL injection exposureReview web server logs for the Unity Connection for unusual SQL syntax in POST request parameters, or examine the HTTP traffic logs for patterns indicating SQL injection attempts.Affected if Unusual SQL-like patterns are observed in web request logs.
The environment is affected if Cisco Unity Connection version 9.1(1) through 9.1(1.2) is installed and its web interface is accessible to the attacker.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch or upgrade Cisco Unity Connection to a version beyond 9.1(1.2) that addresses this vulnerability. If immediate patching is not possible, restrict web interface access to trusted IP addresses and monitor for suspicious SQL-like patterns in requests.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6299 in production — separate from our analysis above.
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.
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.
- 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