dbcve.org
Unified MeetingplaceApplication · Cisco

CVE-2012-5416

HIGH · 7.8 CVSS v2.0 Published 2012-11-02
Fix available
A fix is available. Upgrade to after 7.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Buffer overflow in Cisco Unified MeetingPlace Web Conferencing before 7.1MR1 Patch 1, 8.0 before 8.0MR1 Patch 1, and 8.5 before 8.5MR3 allows remote attackers to cause a denial of service (daemon hang) via unspecified parameters in a POST request, aka Bug ID CSCua66341.

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

A buffer overflow vulnerability exists in Cisco Unified MeetingPlace Web Conferencing software that allows remote attackers to cause denial of service by sending specially crafted parameters in POST requests. The vulnerability affects multiple version branches (7.x, 8.0, and 8.5) prior to their respective patch releases, causing the conferencing daemon to hang.

MitigationApply the vendor-supplied patches: 7.1MR1 Patch 1, 8.0MR1 Patch 1, or 8.5MR3 as appropriate for the deployed version. If patching is not immediately possible, consider restricting access to the web conferencing interface via network segmentation or firewall rules.

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 MeetingplaceApplication
Affected:<= 7.1= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.1= 8.0= 8.5= 8.5.1= 8.5.2= 8.5.3= 8.5.4

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
None
Confidentiality
None
Integrity
None
Availability
Complete

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

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. Verify Cisco Unified MeetingPlace is installed
    Check for the MeetingPlace installation directory (commonly at C:\Program Files\Cisco Systems\MeetingPlace or /opt/cisco/meetingplace on Linux). Look for the 'mpconf' or 'meetingplace' service running on the system.
    Affected if The software is not found on the system, meaning the system is not affected by this CVE.
  2. Identify the installed version
    Locate the version information in the installation directory. On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\MeetingPlace\Version or examine the 'about' page of the web conferencing interface by accessing the MeetingPlace URL.
    Affected if The version matches one of the following: 7.0, 7.0.1, 7.0.2, 7.0.3, 7.1, any version 7.1 or lower, 8.0, 8.5, 8.5.1, 8.5.2, 8.5.3, or 8.5.4.
  3. Confirm the web conferencing service is running
    Verify that the 'Cisco Unified MeetingPlace' web service is active and listening on ports 80 or 443. Check via netstat or by attempting to access the MeetingPlace login page.
    Affected if The web service is running and accessible, making the vulnerability exploitable via crafted POST requests.
  4. Check network exposure of the web interface
    Review firewall rules or network configuration to determine if the MeetingPlace web interface (port 80/443) is exposed to untrusted networks or the internet.
    Affected if The web interface is accessible from untrusted networks, increasing the risk of remote exploitation.

A system is affected if Cisco Unified MeetingPlace version 7.0 through 7.1 (inclusive), 8.0, or 8.5 through 8.5.4 is installed with the web conferencing interface accessible to potential attackers.

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
Upgrade available Upgrade to a release after 7.1
Interim mitigation

Apply the vendor-supplied patches: 7.1MR1 Patch 1, 8.0MR1 Patch 1, or 8.5MR3 as appropriate for the deployed version. If patching is not immediately possible, consider restricting access to the web conferencing interface via network segmentation or firewall rules.

Fix this in Unified Meetingplace Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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