Sensitive-data disclosure via post-logout session reuse
Published Apr 8, 2020 · Updated Sep 16, 2024
Session invalidation failure in IBM Security Information Queue 1.0.0 through 1.0.5 allows remote attackers to read sensitive data. The Web UI leaves a session identifier valid after its user logs out instead of immediately invalidating the token. Exploitation requires obtaining and replaying a logged-out user's session token, and access remains bounded by that session's permissions.
Summary
What happened
Session invalidation failure in IBM Security Information Queue 1.0.0 through 1.0.5 allows remote attackers to read sensitive data. The Web UI leaves a session identifier valid after its user logs out instead of immediately invalidating the token. Exploitation requires obtaining and replaying a logged-out user's session token, and access remains bounded by that session's permissions.
The record
- CVE
- CVE-2020-4291
- Published
- Apr 8, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- Security Verify Information Queue
- Classifications
- CWE-384, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0
- Affected versionversion=1.0.1
- Affected versionversion=1.0.2
- Affected versionversion=1.0.3
- Affected versionversion=1.0.4
- Affected versionversion=1.0.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo