dbcve.org
Xiv Storage System 2810 A14 FirmwareOperating system · Ibm

CVE-2012-2166

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-08
Fix available
A fix is available. Upgrade to 10.2.4.e-2 / 11.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
IBM XIV Storage System 2810-A14 and 2812-A14 devices before level 10.2.4.e-2 and 2810-114 and 2812-114 devices before level 11.1.1 have hardcoded passwords for unspecified accounts, which allows remote attackers to gain user access via unknown vectors. IBM X-Force ID: 75041.

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

Hardcoded passwords embedded in IBM XIV Storage System firmware for unspecified service accounts allow remote attackers to authenticate with administrative privileges. This is a pre-authentication vulnerability exploitable over the network with CVSS vector indicating low attack complexity and complete impact to confidentiality and integrity.

MitigationUpgrade XIV storage devices to firmware version 10.2.4.e-2 or 11.1.1 and later to remove hardcoded credentials. Immediately change any default passwords and restrict network access to management interfaces.

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
Xiv Storage System 2810 A14 FirmwareOperating system
Affected:< 10.2.4.e-2
Xiv Storage System 2812 A14 FirmwareOperating system
Affected:< 10.2.4.e-2
Xiv Storage System 2810 114 FirmwareOperating system
Affected:< 11.1.1
Xiv Storage System 2812 114 FirmwareOperating system
Affected:< 11.1.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 XIV storage system model
    Access the XIV management interface or use the XIV CLI command 'xiv_sysdiag -v' or check the system information screen to confirm the model is either 2810 or 2812
    Affected if Model is 2810 or 2812
  2. Determine the installed firmware version
    Use the XIV management GUI under 'System' > 'Software Version' or run 'lsfver' command via the XIV CLI to retrieve the current firmware version
    Affected if Firmware version cannot be determined or is below 10.2.4.e-2 for A14 models or below 11.1.1 for 114 models
  3. Verify the firmware branch
    Check if the firmware is A14 branch or 114 branch by examining the version string format (A14 versions end with letter designators like 'e-2', 114 versions are numeric like '11.x.x')
    Affected if Running A14 branch version < 10.2.4.e-2 OR 114 branch version < 11.1.1

If the model is 2810 or 2812 and the firmware version is below 10.2.4.e-2 (for A14) or below 11.1.1 (for 114), the system is vulnerable to hardcoded administrative credentials.

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.

dbcve · scoped
Upgrade available Upgrade to 10.2.4.e-2 / 11.1.1 or later
Fixed in 10.2.4.e-211.1.1
Interim mitigation

Upgrade XIV storage devices to firmware version 10.2.4.e-2 or 11.1.1 and later to remove hardcoded credentials. Immediately change any default passwords and restrict network access to management interfaces.

Recommended fix High confidence

Firmware 10.2.4.e-2 or later for 2810-A14/2812-A14 models; Firmware 11.1.1 or later for 2810-114/2812-114 models

  1. 1. Identify the exact model and current firmware version of the IBM XIV Storage System (2810-A14, 2812-A14, 2810-114, or 2812-114)
  2. 2. Download the appropriate firmware upgrade from IBM Fix Central or the IBM support portal (www-01.ibm.com)
  3. 3. For A14 models: Upgrade to firmware level 10.2.4.e-2 or later
  4. 4. For 114 models: Upgrade to firmware level 11.1.1 or later
  5. 5. Schedule the upgrade during a maintenance window as firmware updates may require system downtime
  6. 6. Follow IBM's documented firmware upgrade procedure for XIV storage systems, including proper backup and verification steps
  7. 7. After upgrade, verify the firmware version has been successfully applied
  8. 8. Change any default credentials that may have been hardcoded as recommended by IBM's post-upgrade security guidance
Caveat Firmware upgrades may require downtime and should be tested in a non-production environment first; ensure compatibility with connected systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xiv Storage System 2810 A14 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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