dbcve.org
Qradar Security Information And Event ManagerApplication · Ibm

CVE-2016-2872

MEDIUM · 5.3 CVSS v3.0 Published 2016-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Directory traversal vulnerability in IBM Security QRadar SIEM 7.2.x before 7.2.7 and QRadar Incident Forensics 7.2.x before 7.2.7 allows remote attackers to read arbitrary files via a crafted URL.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Directory traversal vulnerability in IBM Security QRadar SIEM and QRadar Incident Forensics allows remote attackers to read arbitrary files on the host system by using '../' sequences in crafted URLs to traverse outside the intended web root directory.

MitigationUpgrade QRadar SIEM and QRadar Incident Forensics to version 7.2.7 or later to obtain the patch for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qradar Security Information And Event ManagerApplication
Affected:= 7.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4= 7.2.5= 7.2.6
Security Qradar Incident ForensicsApplication
Affected:= 7.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4= 7.2.5= 7.2.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify QRadar SIEM installation
    Run the command 'rpm -q qradar' or check /opt/qradar/version.ini to determine the installed QRadar SIEM version
    Affected if The version listed is 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, or 7.2.6
  2. Identify QRadar Incident Forensics installation
    Run the command 'rpm -q qradar-forensics' or check /opt/qradar/forensics/version.ini to determine the installed QRadar Incident Forensics version
    Affected if The version listed is 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, or 7.2.6
  3. Verify web interface exposure
    Confirm that the QRadar web console (typically port 443 or 8443) is accessible from the network
    Affected if The web interface is exposed and either QRadar SIEM or Incident Forensics is at a vulnerable version

You are affected if either QRadar SIEM or QRadar Incident Forensics is installed at version 7.2.0 through 7.2.6 and the web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade QRadar SIEM and QRadar Incident Forensics to version 7.2.7 or later to obtain the patch for this vulnerability.

Fix this in Qradar Security Information And Event Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-2872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-2872 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data