CVE-2018-1612 json
IBM QRadar Incident Forensics (IBM QRadar SIEM 7.2, and 7.3) could allow a remote attacker to bypass authentication and obtain sensitive in…
published 8y ago modified 4mo ago also EUVD-2018-12191
- cvss
- 5.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 55.7%
- EPSS 55.7% chance of exploitation in 30 days, percentile 99%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
IBM QRadar Incident Forensics (IBM QRadar SIEM 7.2, and 7.3) could allow a remote attacker to bypass authentication and obtain sensitive information. IBM X-Force ID: 144164.
Patch / fix
Is CVE-2018-1612 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/linux/http/ibm_qradar_unauth_rce)
- Published
Exploit prediction
55.67% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/http/ibm_qradar_unauth_rce IBM QRadar SIEM Unauthenticated Remote Code Execution metasploit exploit, excellent rank, 2018-05-28
- EDB-45005 IBM QRadar SIEM - Remote Code Execution (Metasploit) remote, 2018-07-11
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.8 | CVSS:3.0/A:N/AC:L/AV:N/C:L/I:N/PR:N/S:C/UI:N/E:U/RC:C/RL:O |
| CNA | 3.0 | 5.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 3.0 | 5.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- IBM QRadar SIEM
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
www-01.ibm.com
/support/docview.wss?uid=swg22017062
patch, vendor-advisory
-
exploit-db.com
/exploits/45005/
exploit, third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/144164
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2018-1612
- NVD CVE-2018-1612
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.