CVE-2015-2005
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 SIEM 7.1.x before 7.1 MR2 Patch 12 and 7.2.x before 7.2.5 Patch 6 does not properly expire sessions, which allows remote attackers to obtain sensitive information by leveraging an unattended workstation.
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 SIEM versions 7.1.x before 7.1 MR2 Patch 12 and 7.2.x before 7.2.5 Patch 6 fail to properly expire user sessions after inactivity or logout. This session management flaw allows an attacker with physical access to or network proximity to an unattended authenticated workstation to obtain sensitive information through the still-active session, as the session does not terminate as expected.
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.1.0= 7.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed QRadar SIEM versionAccess the QRadar admin console or run 'qversion' command via SSH to retrieve the exact version and patch levelAffected if The version is 7.1.0, 7.2.0, 7.2.1, 7.2.2, 7.2.3, or 7.2.4, or any 7.1.x version before MR2 Patch 12 or 7.2.x before 7.2.5 Patch 6
-
Locate session management configurationInspect the QRadar configuration files for session timeout settings - typically found in /etc/httpd/conf/ or the Console configuration under Admin > System Settings > Session TimeoutAffected if Session timeout is set to an excessively long duration, zero, or is not explicitly configured
-
Verify session termination behavior after logoutLog in to QRadar, perform activities, click logout, then attempt to access the same session cookie or URL within the expected timeout windowAffected if The session remains active and accessible after logout is clicked, or the session token remains valid longer than the configured timeout period
-
Check for active sessions after inactivity periodLog in, wait beyond the configured inactivity timeout without interaction, then attempt to use the original sessionAffected if The session remains valid and allows access after the expected inactivity period has elapsed
You are affected if your QRadar version falls within 7.1.0 through 7.1 MR2 Patch 11 or 7.2.0 through 7.2.5 Patch 5, and sessions do not expire as expected after inactivity or logout.
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 the vendor patches (7.1 MR2 Patch 12 or 7.2.5 Patch 6) to remediate the improper session expiration. Until patched, enforce strict workstation lock policies and user training to prevent session hijacking from unattended sessions.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2005 — 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-2005 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