Unauthenticated privileged access via OAuth2 client reactivation
Published Apr 13, 2022 · Updated Aug 3, 2024
Authentication bypass in affected VMware Workspace ONE Access releases allows remote attackers to obtain a privileged OAuth2 token. OAuth2TokenResourceController exposes activation-token generation and client activation without authentication, allowing a default OAuth2 client to be reactivated and its secret exchanged for a signed token. Network access to the HTTPS service and an existing default OAuth2 client are sufficient; the token permits operations with that client's privileges.
Summary
What happened
Authentication bypass in affected VMware Workspace ONE Access releases allows remote attackers to obtain a privileged OAuth2 token. OAuth2TokenResourceController exposes activation-token generation and client activation without authentication, allowing a default OAuth2 client to be reactivated and its secret exchanged for a signed token. Network access to the HTTPS service and an existing default OAuth2 client are sufficient; the token permits operations with that client's privileges.
The record
- CVE
- CVE-2022-22955
- Published
- Apr 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- VMware
- Product
- VMware Workspace ONE Access
- Classifications
- T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Access 21.08.0.1, 21.08.0.0, 20.10.0.1, 20.10.0.0.
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
- OAuth2TokenResourceController activation-token request sequencefunctional · demonstrated
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