dbcve.org
Tivoli Storage Manager FastbackApplication · Ibm

CVE-2010-3759

HIGH · 10.0 CVSS v2.0 Published 2010-10-05
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
FastBackMount.exe in the Mount service in IBM Tivoli Storage Manager (TSM) FastBack 5.5.0.0 through 5.5.6.0 and 6.1.0.0 through 6.1.0.1 writes a certain value to a memory location specified by a UDP packet field, which allows remote attackers to execute arbitrary code via multiple requests. NOTE: this might overlap CVE-2010-3058.

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 FastBackMount.exe component in IBM TSM FastBack's Mount service contains a memory corruption vulnerability where it writes a value to a memory location directly specified by a field within incoming UDP packets. This provides an attacker with controlled arbitrary memory write primitive, which can be chained to achieve remote code execution. The lack of authentication on the UDP protocol exposes this flaw to network-based attackers.

MitigationApply vendor patches for TSM FastBack versions 5.5.x and 6.1.x; if patches are unavailable, disable the Mount service or restrict network access to the UDP port via firewall rules to limit exposure to trusted networks only.

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= 6.1.0.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 if IBM TSM FastBack is installed
    Check the installed programs on the system for 'IBM TSM FastBack', 'Tivoli Storage Manager FastBack', or look for the FastBack installation directory. Use 'Programs and Features' on Windows or check common installation paths.
    Affected if The software is installed and matches one of the affected versions (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, or 6.1.0.1)
  2. Verify the FastBack Mount service is running
    Check for the FastBackMount.exe process in the running processes, or check if the 'IBM TSM FastBack Mount Service' or similar named service is started. Use Task Manager, sc query, or PowerShell Get-Process/Get-Service.
    Affected if The FastBackMount.exe process or Mount service is actively running, exposing the vulnerable component to network traffic
  3. Confirm UDP listener is active on the system
    Use netstat -an or PowerShell Get-NetTCPConnection/Get-NetUDPEndpoint to check for UDP listeners associated with FastBack. Look for any UDP port listening that corresponds to the FastBack Mount service.
    Affected if A UDP port is open and listening, which indicates the vulnerable service is reachable and awaiting UDP packets
  4. Compare installed version against affected ranges
    Right-click the FastBackMount.exe file, select Properties, and check the File Version on the Details tab. Alternatively, check the version through the FastBack administrative console or registry under the FastBack installation keys.
    Affected if The installed version exactly matches one of the versions listed in the affected products list

The system is affected if IBM TSM FastBack is installed with a version matching 5.5.x or 6.1.0.0/6.1.0.1, the FastBackMount.exe process is running, and a UDP listener is active exposing the service to network traffic.

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

Apply vendor patches for TSM FastBack versions 5.5.x and 6.1.x; if patches are unavailable, disable the Mount service or restrict network access to the UDP port via firewall rules to limit exposure to trusted networks only.

Recommended fix Moderate confidence

IBM TSM FastBack 5.5.6.1 or later (5.5.x line); IBM TSM FastBack 6.1.0.2 or later (6.1.x line); or migrate to latest supported FastBack 6.x release

  1. 1. Identify the current installed version of IBM Tivoli Storage Manager FastBack by checking the FastBackMount.exe version or using the IBM FastBack administrator console.
  2. 2. If running version 5.5.x (5.5.0.0 through 5.5.6.0), plan to upgrade to version 5.5.6.1 or later, or migrate to a supported later major version such as 6.1.x or 6.3.x.
  3. 3. If running version 6.1.0.0 through 6.1.0.1, upgrade to version 6.1.0.2 or later, or migrate to a supported later major version such as 6.3.x.
  4. 4. Download the updated IBM Tivoli Storage Manager FastBack installation media from IBM Fix Central (https://www.ibm.com/support/fixcentral/).
  5. 5. Before applying the upgrade, perform a complete backup of the FastBack server configuration and all backup data.
  6. 6. Stop all FastBack services, including the FastBack Mount service, using the IBM FastBack service manager or Windows Services console.
  7. 7. Install the upgraded FastBack version following the IBM installation guide for your specific version.
  8. 8. After installation, verify that FastBackMount.exe is updated and the service starts successfully.
Caveat Upgrading TSM FastBack may require configuration adjustments; ensure compatibility with existing backup clients and storage systems before production deployment

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

Fix this in Tivoli Storage Manager Fastback Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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