Loading vulnerability…
IBM QRadar Incident Forensics in IBM QRadar SIEM 7.2 and 7.3 contains an authentication-bypass vulnerability that could allow a remote attacker to bypass authentication and obtain sensitive information.
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 module (ibm_qradar_unauth_rce.rb) targeting IBM QRadar SIEM systems. The exploit chains three vulnerabilities (CVE-2016-9722, CVE-2018-1418, CVE-2018-1612) in the Forensics web application to achieve unauthenticated remote code execution as root. The attack proceeds in three stages: (1) authentication bypass via session cookie fixation, (2) file upload and execution as the 'nobody' user, and (3) privilege escalation to root by inserting a crafted entry into the QRadar database, which triggers execution of an attacker-controlled shell script. The module is designed to deliver a reverse shell payload (default: generic/shell_reverse_tcp) to the attacker's machine. The exploit interacts with the /ForensicsAnalysisServlet/ endpoint and writes payloads to /store/configservices/staging/updates/ on the target. The code is operational and weaponized for use within the Metasploit framework, requiring only basic configuration of target and listener parameters. The repository is structured as a single Ruby file compatible with Metasploit, and all exploit logic is contained within this 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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.