CVE-2010-3760
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 · uneditedFastBackMount.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 does not properly handle a certain failure to allocate memory, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash, and recovery failure) by specifying a large size value within TCP packet data. NOTE: this might overlap CVE-2010-3061.
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 confidenceFastBackMount.exe in IBM TSM FastBack versions 5.5.0.0-5.5.6.0 and 6.1.0.0-6.1.0.1 fails to properly handle memory allocation failures when processing TCP packets containing large size values, leading to NULL pointer dereference, daemon crash, and denial of service.
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.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.1CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM TSM FastBack installationCheck for the presence of IBM TSM FastBack software on the system. Look for installation directories typically under C:\Program Files\IBM\Tivoli\TSM\FastBack or similar paths, or check Windows Add/Remove Programs for IBM Tivoli Storage Manager FastBack entry.Affected if The product is not installed or the installation cannot be found.
-
Identify installed FastBack versionLocate the FastBackMount.exe file (commonly in the FastBack installation directory under Mount or bin subfolder) and check its file version. Right-click the file, select Properties, and view the Version tab. Alternatively, use command: dir "C:\Program Files\IBM\Tivoli\TSM\FastBack\*\FastBackMount.exe" /s /b to find all instances, then check each file's version property.Affected if Unable to determine the version of FastBackMount.exe.
-
Compare version against affected rangesCompare the installed FastBackMount.exe version to the affected ranges: 5.5.0.0 through 5.5.6.0, and 6.1.0.0 through 6.1.0.1. Ensure the full version string matches one of these exact versions or falls within these ranges.Affected if The installed version is 5.5.0.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.
-
Confirm FastBackMount service is exposed to networkVerify the FastBackMount service is running and listening on TCP ports. Use netstat -an | findstr "LISTENING" to check for ports associated with FastBack (commonly port 3100 or similar). The vulnerability is triggered by specially crafted TCP packets, so network exposure increases risk.Affected if The FastBackMount service is running and accessible over the network.
If the installed TSM FastBack version matches 5.5.0.0-5.5.6.0 or 6.1.0.0-6.1.0.1 and the FastBackMount.exe component is present and network-accessible, the environment is affected by this CVE.
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 dataApply IBM vendor patches for TSM FastBack or upgrade to a version beyond 6.1.0.1 that includes the fix; network filtering can provide interim protection.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3760 — 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-3760 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