CVE-2019-4072
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 Tivoli Storage Productivity Center (IBM Spectrum Control Standard Edition 5.2.1 through 5.2.17) allows users to remain idle within the application even when a user has logged out. Utilizing the application back button users can remain logged in as the current user for a short period of time, therefore users are presented with information for Spectrum Control Application. IBM X-Force ID: 157064.
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 Tivoli Storage Productivity Center (Spectrum Control 5.2.1-5.2.17) contains a session management vulnerability where user sessions are not properly invalidated upon logout. After logging out, the application allows continued access through the browser back button for a short period, exposing sensitive Spectrum Control application data to unauthorized 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>= 5.2.8, <= 5.2.17.2>= 5.3.0, <= 5.3.1>= 5.2.0, <= 5.2.7.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 installed IBM Spectrum Control or Tivoli Storage Productivity Center versionCheck the product version through the Web GUI (usually in About or Help section) or by inspecting the installation directory for version files. Common locations include /opt/IBM/SPC or the Windows equivalent installation folder.Affected if Installed version falls within >= 5.2.8 <= 5.2.17.2, >= 5.3.0 <= 5.3.1 for Spectrum Control, or >= 5.2.0 <= 5.2.7.1 for Tivoli Storage Productivity Center
-
Verify logout does not invalidate server-side sessionLog into the application, then log out. Use a tool or browser to inspect if the session ID remains valid server-side by attempting to access an authenticated API endpoint with the previous session cookie.Affected if After logout, the server still accepts the previous session ID and returns valid authenticated data instead of redirecting to login
-
Check for missing cache-control headers on authenticated pagesCapture HTTP response headers from an authenticated page using browser developer tools or a proxy. Inspect the response headers for cache-control directives like no-store, no-cache, or must-revalidate.Affected if Authenticated pages lack proper cache-control headers to prevent browser caching, allowing back-button access to cached content after logout
-
Inspect session cookie expiration behaviorExamine the session cookie (typically named like JSESSIONID or similar) before and after logout using browser developer tools or HTTP traffic capture.Affected if Session cookie is not expired or invalidated immediately upon logout action
You are affected if your installed version is within the listed ranges AND you can access authenticated content or data via browser back button after logging out, indicating sessions are not properly invalidated.
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 dataImplement immediate session invalidation on logout and configure proper cache-control headers to prevent back-button caching of authenticated content. Verify all server-side session state is destroyed and client-side session cookies are expired on logout.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4072 — 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-2019-4072 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