Unified MeetingplaceApplication · Cisco

CVE-2012-0337

MEDIUM · 6.5 CVSS v2.0 Published 2012-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
SQL injection vulnerability in the web component in Cisco Unified MeetingPlace 7.1 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, aka Bug ID CSCtx08939.

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 · moderate confidence

SQL injection vulnerability in the web component of Cisco Unified MeetingPlace version 7.1 allows remote authenticated users to execute arbitrary SQL commands. The vulnerability is network-accessible and requires valid user credentials but does not require user interaction. This is a classic SQL injection flaw where user-supplied input is not properly sanitized before being used in database queries.

MitigationApply available patches from Cisco for Unified MeetingPlace 7.1. If no patch is available, implement input validation and parameterized queries in the web component code, and restrict database permissions for the application account to least privilege.

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

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 checks

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

  1. Verify Cisco Unified MeetingPlace version
    Locate the installed version of Cisco Unified MeetingPlace by checking the system management interface, application logs, or using the 'show version' command in the MeetingPlace administrative CLI. Alternatively, check the About or System Information page in the web administration portal.
    Affected if The installed version is exactly 7.1 (7.1.0) and has not been patched.
  2. Confirm the web component is enabled
    Access the web administration interface of Cisco Unified MeetingPlace and navigate to System Settings or Service Configuration. Verify whether the web component/service is enabled and listening on HTTP/HTTPS ports (typically ports 80, 443, or custom web ports).
    Affected if The web component is enabled and accessible over the network.
  3. Check for external network accessibility
    Review firewall rules, ACLs, and network configuration to determine if the web component port is exposed to untrusted networks or the public internet. Use network scanning tools to confirm which interfaces the web service is listening on.
    Affected if The web interface is reachable from untrusted network segments or the internet.
  4. Determine if authentication is required for access
    Test access to the web component login page from an unauthenticated perspective. Verify whether the application requires valid user credentials before allowing access to any functional area.
    Affected if The web component allows access to any authenticated user area without additional controls.

A system is affected if it runs Cisco Unified MeetingPlace version 7.1 with the web component enabled and accessible, regardless of whether it is on an internal or external network, since the flaw can be exploited by any valid authenticated user.

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

Apply available patches from Cisco for Unified MeetingPlace 7.1. If no patch is available, implement input validation and parameterized queries in the web component code, and restrict database permissions for the application account to least privilege.

Fix this in Unified Meetingplace Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0337 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