CVE-2015-1994
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 does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.
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 7.2.x before 7.2.5 Patch 5 fails to set the HTTPOnly flag on session cookies in Set-Cookie headers. This allows client-side scripts to access the session cookie via document.cookie, enabling cross-site scripting (XSS) attacks to steal session credentials.
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 QRadar Incident Forensics versionLocate the version information for the QRadar Incident Forensics installation (typically via the product's about, version, or system information interface)Affected if The installed version matches 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, or 7.2.5
-
Verify session cookie configurationIntercept or capture an HTTP response from the application that includes a Set-Cookie header for a session identifier (such as a session ID or authentication token)Affected if The Set-Cookie header for session cookies lacks the HttpOnly attribute (the header shows no 'HttpOnly' flag present)
-
Test JavaScript access to session cookieUsing a browser or testing tool with JavaScript execution capability, attempt to access document.cookie and verify whether the session cookie value is visible to client-side scriptsAffected if The session cookie value appears in document.cookie output, confirming it is accessible to client-side JavaScript
A system is affected if it runs QRadar Incident Forensics version 7.2.0 through 7.2.5 and the session cookies are returned without the HttpOnly flag, allowing XSS theft of credentials.
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 dataAdd the HTTPOnly attribute to the Set-Cookie header for the session cookie in the application configuration or code. This prevents JavaScript access while preserving normal cookie functionality for legitimate HTTP requests.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1994 — 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-1994 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