CVE-2010-4606
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 · uneditedUnspecified vulnerability in the Space Management client in the Hierarchical Storage Management (HSM) component in IBM Tivoli Storage Manager (TSM) 5.4.x before 5.4.3.4, 5.5.x before 5.5.3, 6.1.x before 6.1.4, and 6.2.x before 6.2.2 on Unix and Linux allows remote attackers to execute arbitrary commands via unknown vectors, related to a "script execution vulnerability."
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 confidenceA script execution vulnerability in the Space Management client of IBM Tivoli Storage Manager's Hierarchical Storage Management (HSM) component allows remote attackers to execute arbitrary commands on affected Unix and Linux systems. The specific attack vector is unspecified but enables unauthenticated remote code execution.
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>= 5.4.0, < 5.4.3.4>= 5.5.0, < 5.5.3>= 6.1.0, < 6.1.4>= 6.2.0, < 6.2.2CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm TSM client installationLocate IBM Tivoli Storage Manager client binaries - look for dsmc, dsminfo, or tsm command utilities in standard installation directories (/opt/tivoli/tsm, /usr/tivoli/tsm, or check PATH for tsm client binaries)Affected if TSM client is not found on the system, then not affected
-
Identify installed TSM versionRun 'dsminfo -v' or 'dsmc -v' to retrieve the installed Tivoli Storage Manager client version numberAffected if Version falls within any of these ranges: >= 5.4.0 and < 5.4.3.4; >= 5.5.0 and < 5.5.3; >= 6.1.0 and < 6.1.4; or >= 6.2.0 and < 6.2.2 - if so, the system is potentially affected
-
Verify Space Management HSM component is presentCheck for Space Management (HSM) client binaries such as dsmmigrate, dsmj, or HSM-specific processes. Look in the TSM client installation directory for HSM-specific files or run 'dsminfo' to list installed TSM client optionsAffected if Space Management HSM component is installed and enabled - without this component, the specific attack surface does not exist
-
Confirm operating system is Unix or LinuxRun 'uname -a' or check /etc/os-release to identify the operating systemAffected if The affected system is running Unix or Linux - the vulnerability specifically affects these platforms, not Windows TSM clients
The environment is affected if: (1) IBM Tivoli Storage Manager client is installed, (2) the installed version matches one of the vulnerable version ranges, (3) Space Management HSM component is enabled, and (4) the system is Unix or Linux.
Generated from the published advisory. Verify against your own configuration.
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 data5.4.3.45.5.36.1.4
Apply IBM Tivoli Storage Manager patches 5.4.3.4, 5.5.3, 6.1.4, or 6.2.2 (or later) to all affected Space Management client installations on Unix/Linux systems. Network segmentation can limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2010-4606 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-4606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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