CVE-2015-1930 is a stack-based buffer overflow in the server component of IBM Tivoli Storage Manager FastBack 6.1 before 6.1.12. The flaw allows remote attackers to trigger memory corruption via unspecified vectors. Based on the available information, the issue resides in server-side processing of attacker-controlled input and can cause the daemon to crash. No specific vulnerable function or protocol element is identified in the provided content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/misc/ibm_tsm_dos.rb) that exploits a denial of service vulnerability (CVE-2015-1930) in IBM Tivoli Storage Manager FastBack Server. The exploit works by connecting to the target server on TCP port 11460 and sending a specially crafted packet with opcode 0x534, which triggers a crash in the service. The code is written in Ruby and leverages Metasploit's auxiliary and remote TCP modules. The exploit does not provide code execution or privilege escalation, but rather causes a denial of service by crashing the target service. The only fingerprintable endpoint is the default TCP port 11460 used by the vulnerable service. The repository is structured as a typical Metasploit module, with all exploit logic contained in a single Ruby file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.