This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login.
Read the full analysis โ
Q1What is this vulnerability? (Essence + Consequences)
๐จ **Essence**: Wipro Holmes Orchestrator has a **Broken Access Control** flaw. ๐ **Consequences**: Unauthenticated attackers can download sensitive Excel reports (credentials, user data) without logging in.โฆ
๐ก๏ธ **Root Cause**: **Access Control Error**. The API endpoints for downloading Excel files lack proper authentication checks. ๐ซ No password/token required to access `processexecution/DownloadExcelFile/...` paths.
Q3Who is affected? (Versions/Components)
๐ข **Affected**: **Wipro Holmes Orchestrator**. ๐ฆ **Version**: Specifically **20.4.1** (Build 20.4.1_02_11_2020). If you are on this version, you are at risk!
Q4What can hackers do? (Privileges/Data)
๐ป **Attacker Actions**: Download arbitrary Excel reports. ๐ Includes: Domain Credential Reports, User Reports, Process Reports, Infrastructure Reports, and Resolver Reports.โฆ
โก **Exploitation Threshold**: **LOW**. ๐ช No authentication needed. Just send a GET request to the specific API endpoint. Anyone on the internet can access it if the port is open.
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ **Public Exploit**: **YES**. ๐ A Nuclei template exists on GitHub (projectdiscovery/nuclei-templates). PacketStorm also has a disclosure. Easy to automate and scan.
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: Use **Nuclei** with the CVE-2021-38147 template. ๐งช Or manually curl the endpoint: `.../processexecution/DownloadExcelFile/Domain_Credential_Report_Excel`. If you get an Excel file, you are vulnerable!
Q8Is it fixed officially? (Patch/Mitigation)
๐ฉน **Official Fix**: The data implies a vulnerability exists in 20.4.1. ๐ Check Wipro's official site for updates. Usually, upgrading to a patched version is the only real fix for access control flaws.
Q9What if no patch? (Workaround)
๐ง **No Patch?**: **Mitigation**: Block external access to these API endpoints via **Firewall/WAF**. ๐ Restrict IP access to internal networks only. Remove public exposure of `/processexecution/` paths.
Q10Is it urgent? (Priority Suggestion)
๐ฅ **Urgency**: **HIGH**. ๐จ Critical data (credentials/reports) is exposed with zero effort. Patch immediately or isolate the service. Don't wait!