# CVE-2018-1612: Auth bypass in QRadar SIEM

> Remote attackers can bypass authentication in IBM QRadar Incident Forensics to access sensitive information.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6gph-3ccw-c7m6

## What is CVE-2018-1612?

CVE-2018-1612 is a medium-severity authentication bypass vulnerability in Ibm Qradar Security Information and Event Manager, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-1612?

It affects 1 product.


Products: Ibm Qradar Security Information and Event Manager.

## How do I fix CVE-2018-1612?

No fix has been published for CVE-2018-1612 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1612 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1612 exists.

Public exploit code:

- IBM QRadar SIEM Unauthenticated Remote Code Execution (metasploit)
- IBM QRadar SIEM - Remote Code Execution (Metasploit) (exploitdb)
- IBM QRadar SIEM - Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Ibm Qradar Security Information and Event Manager

- [CVE-2019-4210](https://insights.sbomify.com/CVE-2019-4210/): Auth bypass in QRadar SIEM (critical 9.4)
- [CVE-2014-3062](https://insights.sbomify.com/CVE-2014-3062/): Code injection in n/a (critical 9.3)
- [CVE-2025-33117](https://insights.sbomify.com/CVE-2025-33117/): IBM QRadar SIEM command execution (critical 9.1)
- [CVE-2020-4512](https://insights.sbomify.com/CVE-2020-4512/): Command injection in QRadar SIEM (critical 9.1)
- [CVE-2015-2011](https://insights.sbomify.com/CVE-2015-2011/): Command injection in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1612 and fix it if it is affected.

What it is: CVE-2018-1612 is a medium-severity authentication bypass vulnerability in Ibm Qradar Security Information and Event Manager, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1612 exists.

Affected product: Ibm Qradar Security Information and Event Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1612/ (Markdown: https://insights.sbomify.com/CVE-2018-1612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1612
- OSV: https://osv.dev/vulnerability/CVE-2018-1612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1612/
Summaries are generated and may contain mistakes; the official description above is the record.