cve.bz

CVE-2018-1649 ibm qradar incident forensics: Path traversal

6.5 mediumEPSS 2.5%Fix available

Medium (6.5) in ibm qradar incident forensics. EPSS 2.5% estimated probability of exploitation activity in the next 30 days.

On this page
IBM QRadar Incident Forensics 7.2 and 7.3 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 144655.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
2.5% (unchanged from 2.5% a week ago; 2.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 85th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-1649 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-1649?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-1649?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-1649 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ibm:qradar_incident_forensics7.2.8:patch1
ibm:qradar_incident_forensics7.2.8:patch13
ibm:qradar_incident_forensics7.2.8:patch8
ibm:qradar_incident_forensics7.3.1:patch3
ibm:qradar_incident_forensics7.3.1:patch4
ibm:qradar_incident_forensicsfrom 7.2.0 through 7.2.8
ibm:qradar_incident_forensicsfrom 7.3.0 through 7.3.1

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON