Loading vulnerability…
A vulnerability in IBM Sterling B2B Integrator Standard Edition versions 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.2 allows an attacker on the local network to execute arbitrary code on the affected system. The vulnerability is due to insecure deserialization of untrusted data, which can be exploited to achieve remote code execution.
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 provides a proof-of-concept (PoC) exploit for vulnerabilities in IBM Sterling B2B Integrator (versions 6.2.0.0 to 6.2.0.2 and 6.0.0.0 to 6.1.2.5) affecting Linux, Windows, and AIX platforms. The main focus is on a local privilege escalation (LPE) command injection and a pre-authentication deserialization remote code execution (RCE) vulnerability (CVE-2024-31903). The Java file `Main.java` constructs and sends a serialized Java object to a CLA2 client, which, if vulnerable, will execute arbitrary shell commands provided by the attacker. The Python script `bin_client.py` can send crafted serialized messages to a target CLA2 client over TCP. The repository also includes a Python reverse shell (`revshell.py`) and a listener (`revshell_listener.py`) to facilitate post-exploitation interactive access. The exploit requires the attacker to have access to certain IBM-proprietary Java classes, which are not included and must be obtained from the target installation. The attack vector is network-based, targeting a listening CLA2 client, and the exploit can be used to execute arbitrary commands or obtain a reverse shell on the target system.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.