Login access token disclosure through insufficient protection
Published Jul 26, 2022 · Updated Sep 16, 2024
Information disclosure in IBM Robotic Process Automation 21.0.0 through 21.0.2 allows physically proximate attackers to obtain a login access token. IBM identifies insufficient protection of the token on the Windows client, but has not disclosed the storage location or extraction operation. Access to the local client host is required, and the exposed token permits login as the account represented by that token.
Summary
What happened
Information disclosure in IBM Robotic Process Automation 21.0.0 through 21.0.2 allows physically proximate attackers to obtain a login access token. IBM identifies insufficient protection of the token on the Windows client, but has not disclosed the storage location or extraction operation. Access to the local client host is required, and the exposed token permits login as the account represented by that token.
The record
- CVE
- CVE-2022-22412
- Published
- Jul 26, 2022
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Robotic Process Automation
- Classifications
- T1528
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2022CVE 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=21.0.0
- Affected versionversion=21.0.1
- Affected versionversion=21.0.2
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