dbcve.org
System Storage Ts3100 Ts3200 Tape LibraryApplication · Ibm

CVE-2016-9005

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 System Storage TS3100-TS3200 Tape Library could allow an unauthenticated user with access to the company network, to change a user's password and gain remote access to the system.

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

IBM System Storage TS3100-TS3200 Tape Library contains an authentication bypass vulnerability allowing unauthenticated attackers on the company network to change any user's password, thereby gaining full remote administrative access to the tape library system.

MitigationRestrict network access to management interfaces via firewall rules or VLAN segmentation, and apply IBM-supplied firmware patches for this vulnerability.

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
System Storage Ts3100 Ts3200 Tape LibraryApplication
Affected:<= d.60

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 tape library model
    Locate the physical hardware or check system documentation to confirm the model is IBM System Storage TS3100 or TS3200 Tape Library
    Affected if The model is TS3100 or TS3200
  2. Check the installed firmware version
    Access the tape library management interface or use the native IBM utility to query the firmware version. Compare it to the affected version d.60
    Affected if The firmware version is d.60 or lower
  3. Verify if remote management interface is enabled
    Check the tape library configuration settings for web-based or remote administrative access. Confirm whether the management Ethernet port is connected to the network
    Affected if Remote management or web admin interface is enabled and accessible on the network
  4. Confirm network accessibility of management ports
    Review network configuration to determine if the tape library management ports (typically HTTP/HTTPS) are reachable from the company network rather than isolated
    Affected if Management interface is reachable from untrusted network segments

A user is affected if they have a TS3100 or TS3200 tape library with firmware version d.60 or lower and its management interface is accessible from the company network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to management interfaces via firewall rules or VLAN segmentation, and apply IBM-supplied firmware patches for this vulnerability.

Recommended fix Moderate confidence

IBM System Storage TS3100/TS3200 Tape Library firmware version d.70 or later (post-d.60 release containing security fix)

  1. 1. Identify the current firmware version of the IBM System Storage TS3100 or TS3200 Tape Library by accessing the library management interface or checking the product label.
  2. 2. Navigate to IBM Support and Downloads for the TS3100/TS3200 Tape Library firmware.
  3. 3. Download the latest IBM firmware version for the tape library (versions after d.60 contain the security fix).
  4. 4. Follow IBM's documented firmware upgrade procedure, which typically requires: connecting to the library via web interface or SSH, navigating to the firmware update section, uploading the firmware file, and allowing the system to reboot into the new firmware.
  5. 5. After upgrade, verify the new firmware version is installed and confirm the password change vulnerability is remediated by testing that unauthenticated password modification is no longer possible.
  6. 6. Ensure default administrative credentials are changed after the upgrade and follow IBM's password policy recommendations.
Caveat Review IBM release notes for the target firmware version to check for any compatibility changes with backup software or library management tools; some legacy interface support may be deprecated in newer firmware.

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

Fix this in System Storage Ts3100 Ts3200 Tape Library Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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