Session hijacking via retained session identifiers
Published Feb 2, 2022 · Updated Sep 17, 2024
Session fixation in IBM Financial Transaction Manager for SWIFT Services 3.2.4 allows remote authenticated users to hijack sessions. The user interface retains an existing session identifier when authentication establishes the session, leaving that identifier valid afterward. Low-privilege access and knowledge of an existing identifier are required; reuse grants the authenticated session's permissions.
Summary
What happened
Session fixation in IBM Financial Transaction Manager for SWIFT Services 3.2.4 allows remote authenticated users to hijack sessions. The user interface retains an existing session identifier when authentication establishes the session, leaving that identifier valid afterward. Low-privilege access and knowledge of an existing identifier are required; reuse grants the authenticated session's permissions.
The record
- CVE
- CVE-2021-39066
- Published
- Feb 2, 2022
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 2, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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