User impersonation via post-change session persistence
Published Jan 4, 2023 · Updated Apr 10, 2025
Session expiration failure in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.0 allows remote authenticated users to impersonate users. The Dashboard keeps an existing authenticated session valid after the associated account password changes, so the session remains accepted despite credential rotation. IBM has not disclosed how an authenticated user obtains or binds another user's surviving session; the bounded consequence is user impersonation.
Summary
What happened
Session expiration failure in IBM Sterling B2B Integrator 6.0.0.0 through 6.1.2.0 allows remote authenticated users to impersonate users. The Dashboard keeps an existing authenticated session valid after the associated account password changes, so the session remains accepted despite credential rotation. IBM has not disclosed how an authenticated user obtains or binds another user's surviving session; the bounded consequence is user impersonation.
The record
- CVE
- CVE-2022-22371
- Published
- Jan 4, 2023
- Updated
- Apr 10, 2025
- Vendor
- IBM
- Product
- IBM Sterling B2B Integrator
- Classifications
- CWE-613, T1550.004
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 4, 2023CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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=6.0.0.0 <6.1.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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