CVE-2015-1964
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 · uneditedStack-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-1929, CVE-2015-1930, CVE-2015-1948, CVE-2015-1953, CVE-2015-1954, CVE-2015-1962, CVE-2015-1963, 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 · high confidenceStack-based buffer overflow in IBM Tivoli Storage Manager FastBack server (versions before 6.1.12) allows remote attackers to crash the daemon via unspecified vectors, causing 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= 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.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 Tivoli Storage Manager FastBack is installedLocate the FastBack installation directory or check system inventory for IBM Tivoli Storage Manager FastBack componentAffected if The product is not installed on the system
-
Determine the installed FastBack server versionRun the appropriate version command or check version information in the FastBack installation (such as about dialog, version file, or command-line query)Affected if Unable to retrieve version information
-
Compare installed version against affected versionsCompare your installed version to the list of 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, 6.1.11.1, or any version prior to 6.1.12Affected if Your installed version matches any version before 6.1.12 from the affected list or is earlier than 6.1.12
-
Confirm the FastBack server daemon is runningCheck the status of the FastBack server service or process to verify it is activeAffected if The server daemon is running and your version is in the affected range
You are affected if IBM Tivoli Storage Manager FastBack server is installed and the running version is any of the listed versions (6.1.0.0 through 6.1.11.1) or earlier than 6.1.12.
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 dataUpgrade IBM Tivoli Storage Manager FastBack to version 6.1.12 or later to resolve the vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1964 — 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-2015-1964 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