dbcve.org
Tivoli Storage Manager FastbackApplication · Ibm

CVE-2015-1929

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
Stack-based buffer overflow in the server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to cause a denial of service (daemon crash) via unspecified vectors, a different vulnerability than CVE-2015-1924, CVE-2015-1925, CVE-2015-1930, CVE-2015-1948, CVE-2015-1953, CVE-2015-1954, CVE-2015-1962, CVE-2015-1963, CVE-2015-1964, and CVE-2015-1965.

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

A stack-based buffer overflow vulnerability exists in the IBM Tivoli Storage Manager FastBack server component affecting versions prior to 6.1.12. This flaw allows remote attackers to cause a denial of service by crashing the daemon through unspecified vectors.

MitigationUpgrade IBM Tivoli Storage Manager FastBack to version 6.1.12 or later to patch this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of the FastBack server.

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

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

  1. Confirm IBM Tivoli Storage Manager FastBack server is installed
    Locate the FastBack server installation directory. Common paths include C:\Program Files\IBM\Tivoli\TSM\FastBack on Windows or /opt/IBM/Tivoli/TSM/FastBack on Linux/Unix. Check for the existence of the FastBack server executable (typically named FBserver.exe, fbsrv, or similar) or the installation directory.
    Affected if The FastBack server component is not installed on the system.
  2. Identify the FastBack server version
    Run the FastBack server version command. On Windows, right-click the FBserver.exe file, select Properties, and check the Version tab. On Linux/Unix, run: /opt/IBM/Tivoli/TSM/FastBack/bin/FBserver -version or consult the About dialog in the FastBack administrative console. Alternatively, check the version recorded in the FastBack installation logs or registry entries.
    Affected if The installed version cannot be determined or is not visible.
  3. Compare installed version against affected versions
    Verify the exact version number obtained in the previous step against the affected version list: 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. Note that version 6.1.12 and later are NOT affected.
    Affected if The installed version matches any version in the affected list (6.1.0.0 through 6.1.11.1).
  4. Verify the FastBack server service is active
    Check if the FastBack server daemon is running. On Windows, open Services console and look for 'IBM Tivoli Storage Manager FastBack Server' or use command: sc query FBserver. On Linux/Unix, run: ps -ef | grep -i fastback or check the process list for the FastBack server process.
    Affected if The FastBack server service is currently running and the version is in the affected range.

If the IBM Tivoli Storage Manager FastBack server is installed and running version 6.1.0.0 through 6.1.11.1, the environment is vulnerable to the stack-based buffer overflow that can crash the daemon.

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 to patch this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of the FastBack server.

Fix this in Tivoli Storage Manager Fastback Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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