Account impersonation via brute-forced LTPA token key
Published May 17, 2022 · Updated Sep 17, 2024
Identity spoofing in IBM WebSphere Application Server Liberty 17.0.0.3 through 22.0.0.5 allows remote authenticated users to impersonate other users. The LTPA token design permits brute-force extraction of the token encryption key and accepts a replacement username in a forged token. Exploitation requires an affected appSecurity feature and authenticated access; the forged identity receives the target user's application privileges.
Summary
What happened
Identity spoofing in IBM WebSphere Application Server Liberty 17.0.0.3 through 22.0.0.5 allows remote authenticated users to impersonate other users. The LTPA token design permits brute-force extraction of the token encryption key and accepts a replacement username in a forged token. Exploitation requires an affected appSecurity feature and authenticated access; the forged identity receives the target user's application privileges.
The record
- CVE
- CVE-2022-22475
- Published
- May 17, 2022
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM WebSphere Application Server Liberty
- Classifications
- T1606
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.0.0.3
- Affected versionversion=22.0.0.5
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