CVE-2015-1999
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 · uneditedIBM Security QRadar Incident Forensics 7.2.x before 7.2.5 Patch 5 places session IDs in https URLs, which allows remote attackers to obtain sensitive information by reading (1) web-server access logs, (2) web-server Referer logs, or (3) the browser history.
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 confidenceIBM Security QRadar Incident Forensics stores session IDs in HTTPS URLs instead of using secure cookies, exposing session identifiers through web-server access logs, Referer headers, and browser history. This allows remote attackers to hijack sessions by harvesting leaked session IDs from these log sources.
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= 7.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4= 7.2.5CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of QRadar Incident ForensicsUse the product's version reporting tool or check the /opt/qradar/www/webapps/forensics/version file if accessible. Run 'rpm -q qradar-incident-forensics' or consult the QRadar admin console for version information.Affected if The version is 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, or 7.2.5.
-
Inspect HTTPS request URLs for session identifiersExamine browser developer tools (Network tab) or capture HTTP traffic while authenticating to the Forensics interface. Look for session-related parameters in the URL such as jsessionid, sessionId, sid, or PHPSESSID.Affected if Session identifiers appear as URL parameters after authentication rather than being managed via cookies.
-
Review web-server access logs for session IDs in URLsExamine the Apache or Nginx access logs for the Forensics web application, typically found in /var/log/httpd/ or /var/log/nginx/. Search for patterns like 'jsessionid=' or 'sessionId=' in GET request URLs.Affected if Access logs contain URLs with session ID values embedded as query parameters.
-
Check Referer headers for session ID leakageReview proxy logs, firewall logs, or the destination application's access logs for incoming requests where the Referer header contains a URL with a session identifier.Affected if Referer headers in logged requests expose session IDs from the Forensics application.
If the installed QRadar Incident Forensics version is between 7.2.0 and 7.2.5 inclusive and session identifiers are visible in URLs, access logs, or Referer headers, the environment is affected by this session ID exposure vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataMigrate session management from URL-based to cookie-based storage using secure, httpOnly, and SameSite attributes to prevent session ID exposure in URLs and logs.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1999 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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