Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PRP: Request CVE-2022-22972 VMware Workspace ONE Access, Identity Manager and vRealize Automation Authentication Bypass #257

Closed
C4o opened this issue May 27, 2022 · 2 comments

Comments

@C4o
Copy link
Contributor

C4o commented May 27, 2022

Hi there,

I would like to contribute the implementation for a plugin that detects CVE-2022-22972. It's published in 9 days ago. VMware Workspace ONE Access, Identity Manager and vRealize Automation contain an authentication bypass vulnerability affecting local domain users. A malicious actor with network access to the UI may be able to obtain administrative access without the need to authenticate.

Vulnerability details:

Score: 9.8 CRITICAL
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References:
https://nvd.nist.gov/vuln/detail/CVE-2022-22972
https://www.vmware.com/security/advisories/VMSA-2022-0014.html
https://www.horizon3.ai/vmware-authentication-bypass-vulnerability-cve-2022-22972-technical-deep-dive/
https://github.com/horizon3ai/CVE-2022-22972/blob/main/CVE-2022-22972.py

The vulnerability should be remotely exploitable without authentication and user interaction. Yes.

The detector should provide a reliable false-positive free detection report. Yes.

The detection capability should be easy to verify using both vulnerable and fixed Docker images. Yes.

The vulnerability should have a relatively large impact radius. Yes.

Please let me know if this is in scope as I've already made the development .

Thanks,
C4o

@maoning
Copy link
Collaborator

maoning commented Jul 18, 2022

Hi @C4o,

Thanks for your request! This vulnerability is in scope for the reward program. Please submit our participation form and you can start working on the development.

Please keep in mind that the Tsunami Scanner Team will only be able to work at one issue at a time for each participant so please hold on the implementation work for any other requests you might have.

Thanks!

@C4o
Copy link
Contributor Author

C4o commented Jul 19, 2022

Hi @maoning, I found #245 is still not reviewed for not having docker enviroment and this issue is the same product.
So I wonder whether I need to go on. If not, can you choose another issue?

@C4o C4o closed this as completed Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants