dbcve.org
Tivoli Storage Manager FastbackApplication · Ibm

CVE-2015-1941

HIGH · 7.8 CVSS v2.0 Published 2015-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to read arbitrary files via a crafted TCP packet to an unspecified port.

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 · moderate confidence

IBM Tivoli Storage Manager FastBack server versions prior to 6.1.12 contain a vulnerability allowing unauthenticated remote attackers to read arbitrary files on the host system by sending crafted TCP packets to an unspecified port. This constitutes a critical information disclosure vulnerability enabling potential exposure of sensitive configuration files, credentials, or other system data.

MitigationUpgrade IBM Tivoli Storage Manager FastBack to version 6.1.12 or later. If immediate patching is not feasible, network segmentation and firewall rules restricting access to the affected service port(s) should be implemented as a compensating control.

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:= 6.1.0.0= 6.1.1.0= 6.1.7.2= 6.1.8.0= 6.1.8.1= 6.1.9.0= 6.1.9.1= 6.1.10.0= 6.1.10.1= 6.1.11.0= 6.1.11.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
None
Availability
None

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

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 Tivoli Storage Manager FastBack server is installed
    Inspect the system for IBM Tivoli Storage Manager FastBack server installation directories, services, or processes. Common locations include C:\Program Files\Tivoli\TSMFastBack on Windows or /opt/tivoli/tsm/fastback on Linux/Unix. Check for the FastBack server service or executable.
    Affected if The product is present on the system
  2. Identify the installed FastBack server version
    Locate the version information in the installation directory, typically found in an about dialog, version file, or through the server executable with a version flag. Common file names include fbinstall.ini, fastback.ini, or check the Windows registry under HKLM\SOFTWARE\IBM\Tivoli\Storage Manager FastBack.
    Affected if The version matches one of the affected versions: 6.1.0.0, 6.1.1.0, 6.1.7.2, 6.1.8.0, 6.1.8.1, 6.1.9.0, 6.1.9.1, 6.1.10.0, 6.1.10.1, 6.1.11.0, or 6.1.11.1
  3. Verify the FastBack server service is running
    Check if the FastBack server process is active. On Windows, use Services.msc or tasklist. On Linux/Unix, use ps aux or systemctl status. The service typically runs as 'TSM FastBack Server' or similar.
    Affected if The service is running and listening on a network port, exposing the vulnerable component to network requests
  4. Assess network exposure of the FastBack server port
    Identify which TCP port the FastBack server is listening on using netstat -ano or similar network tools. Determine if this port is accessible from untrusted networks or the internet.
    Affected if The service port is exposed to untrusted network segments, allowing unauthenticated attackers to send crafted packets

The environment is affected if IBM Tivoli Storage Manager FastBack server version 6.1.0.0 through 6.1.11.1 is installed, the service is running, and the port is network-accessible.

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 IBM Tivoli Storage Manager FastBack to version 6.1.12 or later. If immediate patching is not feasible, network segmentation and firewall rules restricting access to the affected service port(s) should be implemented as a compensating control.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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