CVE-2015-1993
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 set the secure flag for unspecified cookies in an https session, which makes it easier for remote attackers to capture these cookies by intercepting their transmission within an http session.
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 Secure flag on certain session cookies during HTTPS sessions. Without this flag, affected cookies may be transmitted over insecure HTTP connections, allowing remote attackers on the same network path to intercept and capture session credentials via man-in-the-middle attacks.
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 versionCheck the product version in the QRadar console or using system commands such as 'rpm -q' or the version display in the admin interface. Common paths include /opt/qradar/ or checking the About section in the web UI.Affected if The installed version is 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, or 7.2.5 (prior to Patch 5).
-
Verify the product is accessible via HTTPSAttempt to access the QRadar Incident Forensics web interface using an HTTPS URL (e.g., https://<hostname>/). Confirm the connection succeeds and the TLS certificate is presented.Affected if HTTPS access is configured and the interface is reachable over HTTPS.
-
Inspect session cookies for the Secure flagLog into the QRadar Incident Forensics web interface over HTTPS, then use a browser developer tool (Network tab) or an HTTP proxy to capture the Set-Cookie headers. Examine each cookie for the 'Secure' attribute in the Set-Cookie response header.Affected if Session cookies (such as JSESSIONID, QRadarCSRF, or authentication tokens) are present WITHOUT the 'Secure' flag in the Set-Cookie header, even when the request was made over HTTPS.
-
Check if HTTP fallback is permittedAttempt to access the same QRadar Incident Forensics URL using plain HTTP (http://<hostname>/). Determine if the server responds or redirects to HTTPS.Affected if The server accepts HTTP connections and does not force a redirect to HTTPS, allowing cookies to potentially traverse an unencrypted channel.
You are affected if the installed QRadar Incident Forensics version is 7.2.0 through 7.2.5 (before Patch 5) and session cookies are missing the Secure flag even during HTTPS sessions, enabling potential credential interception over HTTP.
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 dataApply IBM QRadar Incident Forensics 7.2.5 Patch 5 or later, which properly sets the Secure flag on cookies. Alternatively, upgrade to a currently supported version receiving security updates.
- 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-1993 — 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-1993 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