CVE-2015-1949
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 · uneditedThe server in IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12 allows remote attackers to execute arbitrary commands with SYSTEM privileges via unspecified vectors.
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 confidenceIBM Tivoli Storage Manager FastBack server versions prior to 6.1.12 contain a critical vulnerability allowing unauthenticated remote attackers to execute arbitrary commands with SYSTEM-level privileges. The specific attack vector and vulnerability type are not detailed in available documentation, but the CVSS score of 10 indicates a trivially exploitable flaw with complete system compromise potential.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Tivoli Storage Manager FastBack installationLocate the FastBack server installation directory or check Windows Programs and Features for 'IBM Tivoli Storage Manager FastBack' entry. The version is typically displayed in the program name or can be found in the server's About or version information.Affected if The software is installed on the system
-
Determine the installed FastBack server versionOpen the FastBack server management console or check the server's version information (commonly accessible via the server's About dialog, a version file in the installation directory, or via command line: 'fbmaster -version' or similar). Record the full version number (e.g., 6.1.11.1).Affected if A version number is returned that matches any 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
-
Verify if FastBack server service is running and exposedCheck if the FastBack server process (typically named 'FBserver' or similar) is running. Determine if the server is accessible over the network by identifying open ports associated with FastBack (commonly port 11460 or similar RPC-based ports). Use 'netstat -an' or the Windows Services console to confirm.Affected if The FastBack server service is running and exposed on the network, making it reachable for remote exploitation
-
Confirm the FastBack server is accessible without authenticationReview the FastBack server configuration to verify whether unauthenticated or anonymous access is permitted to the server's administrative interfaces or RPC endpoints.Affected if Unauthenticated network access to the FastBack server is allowed
If IBM Tivoli Storage Manager FastBack server is installed with a version prior to 6.1.12 and the server is running and network-accessible, the environment is affected by CVE-2015-1949 and is at critical risk.
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.
dbcve · scopedUpgrade IBM Tivoli Storage Manager FastBack to version 6.1.12 or later. Given the critical severity and SYSTEM-level access, treat this as an emergency change requiring immediate patching and verification in a non-production environment before production deployment.
IBM Tivoli Storage Manager FastBack 6.1.12 or later
- Backup the current IBM Tivoli Storage Manager FastBack server configuration and data
- Download IBM Tivoli Storage Manager FastBack version 6.1.12 or later from IBM Fix Central (www-01.ibm.com)
- Stop the FastBack server service using the Windows Services console or command line (net stop TSMFastBack)
- Run the installer for version 6.1.12 or later with appropriate administrator privileges
- Follow the on-screen installation wizard to complete the upgrade
- After installation, start the FastBack server service (net start TSMFastBack)
- Verify the upgrade was successful by checking the server version and ensuring the service is running properly
- Test that normal backup/restore operations function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1949 — 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-1949 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