dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2015-6312

HIGH · 7.5 CVSS v3.0 Published 2016-04-06
Fix available
A fix is available. Upgrade to 2.50 / 2017-01-06 or later.
See remediation →
84/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
Cisco TelePresence Server 3.1 on 7010, Mobility Services Engine (MSE) 8710, Multiparty Media 310 and 320, and Virtual Machine (VM) devices allows remote attackers to cause a denial of service (device reload) via malformed STUN packets, aka Bug ID CSCuv01348.

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 vulnerability exists in Cisco TelePresence Server 3.1 and related devices (7010, MSE 8710, Multiparty Media 310/320, and VM). The devices improperly handle malformed STUN (Session Traversal Utilities for NAT) packets, causing an uncontrolled device reload that results in denial of service. Attackers can exploit this remotely without authentication.

MitigationOrganizations should filter or block STUN traffic from untrusted external sources at network boundaries and apply vendor-supplied patches or firmware updates when available. For interim mitigation, network-level access controls on UDP port 3478 (STUN) may reduce exposure.

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
Emc Powerscale OnefsOperating system
Affected:= 8.2.2
Jr6150 FirmwareOperating system
Affected:< 2017-01-06
Gs1900 10hp FirmwareOperating system
Affected:< 2.50\(aazi.0\)c0
Keymouse FirmwareOperating system
Affected:= 3.08

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify the device model
    Check the physical device label or log into the management interface to confirm the hardware model (7010, MSE 8710, Multiparty Media 310/320) or verify if running as a virtual machine (VM)
    Affected if The device is a Cisco TelePresence Server model 7010, MSE 8710, Multiparty Media 310, Multiparty Media 320, or the VM version
  2. Check the software version
    Log into the Cisco TelePresence Server administrative interface and navigate to the version or system information page, or use the CLI command 'show version' to retrieve the installed software version
    Affected if The installed version is Cisco TelePresence Server 3.1 or falls within the 3.1 release line
  3. Verify STUN service status
    Check the device configuration to determine if the STUN (Session Traversal Utilities for NAT) service is enabled. This is typically found in the network settings or security configuration section of the management interface
    Affected if STUN service is enabled and the device is listening on UDP port 3478 or has STUN traversal configured
  4. Review network exposure to STUN traffic
    Examine firewall rules, access control lists, or network boundary devices to determine if UDP port 3478 (STUN) traffic from untrusted external sources can reach the TelePresence Server
    Affected if STUN traffic from external/untrusted networks can reach the device without filtering or network-level access controls
  5. Check for unexpected device reloads
    Review system logs, crash logs, or the event history on the TelePresence Server for incidents of unexpected device reloads or restarts, particularly correlating with STUN traffic patterns
    Affected if The device has experienced unexplained reloads or denial of service events that coincide with STUN traffic processing

The environment is affected if running a Cisco TelePresence Server (model 7010, MSE 8710, Multiparty Media 310/320, or VM) version 3.1 with STUN service enabled and exposed to untrusted network traffic on UDP port 3478

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 2.50 / 2017-01-06 or later
Fixed in 2.502017-01-06
Interim mitigation

Organizations should filter or block STUN traffic from untrusted external sources at network boundaries and apply vendor-supplied patches or firmware updates when available. For interim mitigation, network-level access controls on UDP port 3478 (STUN) may reduce exposure.

Fix this in Emc Powerscale Onefs 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-2015-6312 — 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-2015-6312 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