Multiple IBM products vulnerable to RCE and DoS
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Multiple vulnerabilities in IBM database and middleware products enable remote code execution, denial of service, and data compromise.
CERT-FR has published an advisory covering multiple vulnerabilities discovered across several IBM enterprise products. The affected products include IBM Db2 Big SQL, Sterling Connect:Direct Web Services, WebSphere Hybrid Edition, and WebSphere Service Registry and Repository. These vulnerabilities allow attackers to achieve remote code execution, cause denial of service, bypass security policies, compromise data confidentiality, and perform server-side request forgery (SSRF) attacks. Organizations running these products must apply the appropriate security patches and fixes referenced in IBM's security bulletins to mitigate the identified risks.
Mentioned in this report
Detection guidance
WebSphere Java Server Process Spawning Command Shell
WebSphere application server JVM spawning cmd/powershell, a typical post-exploitation sign of RCE against a public-facing IBM WebSphere service. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: WebSphere Java Server Process Spawning Command Shell
description: Detects the IBM WebSphere JVM spawning a command interpreter (cmd, PowerShell,
wscript, etc.), which indicates possible exploitation of a remote code execution
flaw in a public-facing WebSphere product. Generalises on the parent/child relation,
not on any specific CVE payload.
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|contains: \WebSphere\
ParentImage|endswith: \java.exe
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection_parent and selection_child
falsepositives:
- Administrative or deployment scripts invoked from within WebSphere applications
that legitimately shell out
- Custom applications hosted on WebSphere that call batch files for job processing
level: medium
id: 777e9d70-1872-50d9-9f3b-d22370a4f229
status: experimental
author: Vorant
references:
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0748
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0748
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs