Unified Communications Domain ManagerApplication · Cisco

CVE-2014-3281

MEDIUM · 5.0 CVSS v2.0 Published 2014-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The web framework in VOSS in Cisco Unified Communications Domain Manager (CDM) does not properly implement access control, which allows remote attackers to obtain potentially sensitive user information by visiting an unspecified BVSMWeb web page, aka Bug IDs CSCun46071 and CSCun46101.

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

The VOSS web framework in Cisco Unified Communications Domain Manager (CDM) has an improper access control implementation, allowing unauthenticated remote attackers to access sensitive user information by visiting a specific BVSMWeb web page. This is an information disclosure vulnerability stemming from broken access controls.

MitigationApply the Cisco patch for this vulnerability (refer to CSCun46071 and CSCun46101). If no patch is available, restrict network access to the CDM management interface and review access control configurations for the BVSMWeb application.

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 Communications Domain ManagerApplication
Affected:all versions

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
Partial
Integrity
None
Availability
None

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

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. Confirm Cisco CDM is running
    Identify if Cisco Unified Communications Domain Manager is deployed in your environment. Check running services or consult your asset inventory for systems running the CDM product.
    Affected if Cisco Unified Communications Domain Manager is installed and running
  2. Locate the BVSMWeb endpoint
    Access the web interface of your CDM installation and navigate to or attempt to access the BVSMWeb path (typically found under the CDM web administration interface).
    Affected if The BVSMWeb application endpoint is accessible on the CDM server
  3. Test unauthenticated access to user data
    Without providing any login credentials, attempt to access the BVSMWeb page that exposes user information. Observe whether the page loads and displays sensitive user data without requiring authentication.
    Affected if The BVSMWeb page displays sensitive user information without requiring any authentication credentials
  4. Verify access control configuration
    Review the access control settings for the BVSMWeb application within the CDM administration console. Check if there are any rules permitting unauthenticated access to user information pages.
    Affected if Access controls are missing or misconfigured, allowing unauthenticated access to user data

If Cisco Unified Communications Domain Manager is running and the BVSMWeb endpoint is accessible without authentication, exposing sensitive user information, the environment is affected by this CVE.

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 the Cisco patch for this vulnerability (refer to CSCun46071 and CSCun46101). If no patch is available, restrict network access to the CDM management interface and review access control configurations for the BVSMWeb application.

Fix this in Unified Communications Domain Manager 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 help mitigating

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-2014-3281 — 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-2014-3281 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