CVE-2016-6447
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 · uneditedA vulnerability in Cisco Meeting Server and Meeting App could allow an unauthenticated, remote attacker to execute arbitrary code on an affected system. This vulnerability affects the following products: Cisco Meeting Server releases prior to 2.0.1, Acano Server releases prior to 1.8.16 and prior to 1.9.3, Cisco Meeting App releases prior to 1.9.8, Acano Meeting Apps releases prior to 1.8.35. More Information: CSCva75942 CSCvb67878. Known Affected Releases: 1.81.92.0.
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 confidenceA critical remote code execution vulnerability in Cisco Meeting Server and Meeting App allows unauthenticated remote attackers to execute arbitrary code on affected systems. The vulnerability affects multiple product versions including Cisco Meeting Server prior to 2.0.1, Acano Server prior to 1.8.16/1.9.3, and Cisco Meeting App prior to 1.9.8. The CVSS 9.8 score indicates a pre-authentication flaw with network-exploitable remote execution capability.
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= 1.8.0= 1.9.0= 1.8_base= 1.9.0= 2.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed Cisco Meeting Server versionRun 'cms --version' or check the product version through the admin web interface under 'About' or 'System Information' pagesAffected if The version displayed is 1.8.x, 1.9.0, or 2.0.0 (specifically 1.8_base, 1.9.0, or 2.0.0)
-
Identify installed Cisco Meeting App versionCheck the application version through the installed software (Windows: Programs and Features, Mac: Applications folder, or within the app's About/Preferences)Affected if The version displayed is exactly 1.8.0 or 1.9.0
-
Check for Acano Server installation and versionIf the system was migrated from Acano, check the version via 'aco --version' or through the admin interface as Acano Server versions prior to 1.8.16 and 1.9.3 are also affectedAffected if Acano Server version is below 1.8.16 or below 1.9.3
-
Determine if the web admin interface is exposedCheck network configuration to see if port 443 or the admin web interface is accessible from untrusted networksAffected if The admin interface is reachable from the internet or untrusted networks (this vulnerability is pre-authentication and network-exploitable)
You are affected if any Cisco Meeting Server version 1.8_base, 1.9.0, or 2.0.0 is installed, or Cisco Meeting App version 1.8.0 or 1.9.0 is in use, with the admin interface network-accessible.
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.
dbcve · scopedUpgrade Cisco Meeting Server to version 2.0.1 or later, Acano Server to 1.8.16/1.9.3 or later, and Meeting Apps to their respective patched versions (1.9.8 for Cisco, 1.8.35 for Acano). Prioritize internet-facing deployments given the unauthenticated remote exploitation vector.
Cisco Meeting Server 2.0.1+ | Acano Server 1.8.16+ / 1.9.3+ | Cisco Meeting App 1.9.8+ | Acano Meeting App 1.8.35+
- Identify the specific Cisco Meeting Server or Meeting App product and current version running
- Determine which product line applies: Cisco Meeting Server, Acano Server, Cisco Meeting App, or Acano Meeting App
- For Cisco Meeting Server: upgrade to version 2.0.1 or later
- For Acano Server: upgrade to version 1.8.16 or later for 1.8.x line, or version 1.9.3 or later for 1.9.x line
- For Cisco Meeting App: upgrade to version 1.9.8 or later
- For Acano Meeting App: upgrade to version 1.8.35 or later
- After upgrade, verify the new version is running and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6447 — 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-2016-6447 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