Tivoli Storage Manager FastbackApplication · Ibm

CVE-2010-3058

HIGH · 7.5 CVSS v2.0 Published 2010-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Mount service in IBM Tivoli Storage Manager (TSM) FastBack 5.x.x before 5.5.7, and 6.1.0.0, establishes an open UDP port, which might allow remote attackers to overwrite memory locations and execute arbitrary code, or cause a denial of service (application hang), via unspecified vectors.

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 Mount service in IBM Tivoli Storage Manager FastBack 5.x.x before 5.5.7 and 6.1.0.0 establishes an open UDP port without proper input validation, allowing remote attackers to potentially overwrite memory locations and execute arbitrary code or cause a denial of service via unspecified vectors.

MitigationUpgrade to IBM TSM FastBack version 5.5.7 or later. If immediate upgrade is not feasible, restrict network access to the Mount service UDP port using firewall rules or network segmentation.

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
Tivoli Storage Manager FastbackApplication
Affected:= 5.5.0= 5.5.1= 5.5.2= 5.5.2.0= 5.5.3.0= 5.5.4.0= 5.5.5.0= 5.5.6.0= 6.1.0.0

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
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 checks

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

  1. Confirm IBM TSM FastBack is installed
    Locate IBM Tivoli Storage Manager FastBack software on the system. Check Add/Remove Programs, Program Files directory for IBM/TSMFastBack folder, or run system software inventory. The executable is typically named FBService.exe or similar in the installation directory.
    Affected if IBM TSM FastBack software is present on the system
  2. Identify the installed FastBack version
    Check the version of the installed FastBack software. In Windows, right-click the installed program in Add/Remove Programs and select Properties, or check version info in the executable file properties. Compare your version against the affected list: 5.5.0, 5.5.1, 5.5.2, 5.5.2.0, 5.5.3.0, 5.5.4.0, 5.5.5.0, 5.5.6.0, or 6.1.0.0
    Affected if The installed version is any of 5.5.0 through 6.1.0.0 (including the specific versions listed)
  3. Verify the Mount service is running
    Check if the FastBack Mount service is active. Open Services (services.msc) and look for a service named 'TSM FastBack Mount' or similar, or run 'sc query' from command line to list running services containing 'FastBack'
    Affected if The Mount service is currently running on the system
  4. Check for open UDP listeners
    Run 'netstat -an | findstr UDP' from command line or use a network port scanner to enumerate UDP ports in LISTENING or ESTABLISHED state. Correlate any open UDP ports with the FastBack process to identify which are associated with the Mount service.
    Affected if An open UDP port is bound to the FastBack Mount service process

The environment is affected if IBM TSM FastBack version 5.5.0 through 6.1.0.0 is installed, the Mount service is running, and an open UDP port is bound to that service.

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

Upgrade to IBM TSM FastBack version 5.5.7 or later. If immediate upgrade is not feasible, restrict network access to the Mount service UDP port using firewall rules or network segmentation.

Fix this in Tivoli Storage Manager Fastback Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3058 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3058 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