CVE-2016-0340
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 expiration, which allows remote attackers to hijack sessions 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 Identity Manager Virtual Appliance versions 7.0.0.0 through 7.0.1.1 before patch FP0003 improperly handles session expiration, allowing active sessions to remain valid beyond intended timeouts. Attackers can hijack sessions by accessing unattended workstations with active ISIM sessions.
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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 ISIM versionAccess the appliance admin console or check the version via command line (e.g., 'enversion' or similar appliance management command). Look for the build version and patch level information.Affected if 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 and patch FP0003 is not applied.
-
Verify session timeout configurationInspect the session timeout settings in the ISIM administration console under Session Management or Security Configuration. Check both idle timeout and absolute session lifetime values.Affected if Session timeout is set to a long duration or is not being enforced, or if timeout configuration shows sessions remaining active beyond intended limits.
-
Confirm patch FP0003 installationCheck the installed patches or fix pack level in the appliance. This may be visible in the system information, about section, or via command line query of installed fixes.Affected if Patch FP0003 is not listed among installed fixes, indicating the vulnerability remains unpatched.
-
Test session expiration behaviorLog in to ISIM, wait beyond the configured session timeout period, then attempt to use the original session token to perform an action. Observe whether the session remains valid.Affected if Session remains active and functional after the configured timeout has elapsed, confirming the vulnerability is present.
A user is affected if running ISIM version 7.0.0.0 through 7.0.1.1 without patch FP0003 installed and sessions are not expiring as configured.
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 security patch 7.0.1-ISS-SIM-FP0003 or upgrade to a patched version. Configure aggressive session timeouts and implement session invalidation on logout as compensating controls until the patch is applied.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0340 — 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-0340 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