CVE-2016-0339
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 Identity Manager (ISIM) Virtual Appliance 7.0.0.0 through 7.0.1.1 before 7.0.1-ISS-SIM-FP0003 mishandles session identifiers after logout, which makes it easier for remote attackers to spoof users by leveraging knowledge of "traffic records."
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 · moderate confidenceIBM Security Identity Manager Virtual Appliance versions 7.0.0.0 through 7.0.1.1 fail to properly invalidate or regenerate session identifiers upon user logout. Session IDs remain valid or predictable (accessible via 'traffic records'), allowing remote attackers who obtain these session identifiers to hijack user sessions and impersonate authenticated users.
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.0.0.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.1.0= 7.0.1.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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 IBM Security Identity Manager installationLocate the IBM Security Identity Manager Adapter installation directory or check system inventory for 'IBM Security Identity Manager Adapter' componentAffected if The product is present on the system
-
Determine installed versionQuery the installed version of the IBM Security Identity Manager Adapter component using the product's version command, about dialog, or installed-packages listingAffected if The installed version is 7.0.0.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.1.0, or 7.0.1.1
-
Verify session management configurationAccess the IBM Security Identity Manager administrative console and navigate to session management or security policy settingsAffected if Session timeout is not enforced or session ID regeneration on logout is not configured
-
Test session invalidation behaviorAuthenticate as a test user, perform logout, then attempt to reuse the previous session identifier or session cookie to access protected resourcesAffected if The original session identifier remains valid after logout (session hijack possible)
-
Review session identifier handlingExamine traffic records, session logs, or session storage to verify whether session IDs change after user logoutAffected if Session IDs are not regenerated or invalidated upon logout
A user is affected if IBM Security Identity Manager Adapter versions 7.0.0.0 through 7.0.1.1 are installed AND session IDs remain valid after logout, allowing session reuse by an attacker who obtains the identifier.
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 vendor patch 7.0.1-ISS-SIM-FP0003 to remediate the session management flaw. Additionally, implement session timeout policies and consider forcing session ID regeneration on authentication as defense-in-depth.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0339 — 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-2016-0339 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