dbcve.org
Integrated Management ControllerApplication · Cisco

CVE-2014-3348

MEDIUM · 5.0 CVSS v2.0 Published 2014-09-10
Fix available
A fix is available. Upgrade to after 2.2.2 or later.
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 SSH module in the Integrated Management Controller (IMC) before 2.3.1 in Cisco Unified Computing System on E-Series blade servers allows remote attackers to cause a denial of service (IMC hang) via a crafted SSH packet, aka Bug ID CSCuo69206.

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

The SSH module in Cisco's Integrated Management Controller (IMC) before version 2.3.1 on Unified Computing System E-Series blade servers contains a denial-of-service vulnerability. A remote attacker can send a specially crafted SSH packet that causes the IMC to hang, rendering the management interface unavailable. This affects the out-of-band management functionality critical for blade server administration.

MitigationUpgrade the IMC firmware to version 2.3.1 or later to remediate this vulnerability. As an interim control, restrict access to the management network by placing IMC interfaces on a dedicated management VLAN with ACLs limiting SSH access to authorized administration hosts.

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
Integrated Management ControllerApplication
Affected:<= 2.2.2
Unified Computing System E140dHardware / appliance
Affected:all versions
Unified Computing System E140dpHardware / appliance
Affected:all versions
Unified Computing System E140s M1Hardware / appliance
Affected:all versions
Unified Computing System E140s M2Hardware / appliance
Affected:all versions
Unified Computing System E160dHardware / appliance
Affected:all versions
Unified Computing System E160dpHardware / appliance
Affected:all versions
Unified Computing System En120s M2Hardware / appliance
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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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. Identify the UCS E-Series blade server model
    Access the CIMC or IMC web interface or CLI and locate the server model identifier (E140d, E140dp, E140s M1/M2, E160d, E160dp, or En120s M2). This information is typically found in the Hardware Summary or Server Properties page.
    Affected if The server model is any of the following: E140d, E140dp, E140s M1, E140s M2, E160d, E160dp, or En120s M2 (these models are all affected regardless of version).
  2. Access the IMC firmware version
    Log into the Cisco Integrated Management Controller (IMC) web interface or CLI. Navigate to the Firmware Management or Software Version page to retrieve the current IMC firmware version.
    Affected if The IMC firmware version is 2.2.2 or earlier.
  3. Verify SSH is enabled on IMC
    In the IMC web interface, go to Network Settings or Services and confirm the SSH service is enabled. Alternatively, from the IMC CLI run 'show services' to list enabled services.
    Affected if SSH is enabled and accessible on the IMC management interface (this is the attack vector).

Your environment is affected if you run a Cisco UCS E-Series blade server (E140d, E140dp, E140s M1/M2, E160d, E160dp, or En120s M2) with IMC firmware version 2.2.2 or earlier and have SSH enabled on the IMC interface.

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 2.2.2
Interim mitigation

Upgrade the IMC firmware to version 2.3.1 or later to remediate this vulnerability. As an interim control, restrict access to the management network by placing IMC interfaces on a dedicated management VLAN with ACLs limiting SSH access to authorized administration hosts.

Fix this in Integrated Management Controller Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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