Executive Summary

This vulnerability exists in SohuTV CacheCloud up to version 3.2.0, specifically in the index function of the ResourceController.java file. It allows an attacker to perform cross-site scripting (XSS) attacks by manipulating inputs. The attack can be initiated remotely, and the exploit has been made public.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to cross-site scripting attacks, which may allow attackers to execute malicious scripts in the context of a user's browser. This can result in unauthorized actions, such as session hijacking or defacement, potentially compromising user trust and security.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by sending crafted HTTP requests to the vulnerable endpoint `/manage/app/resource/index` with malicious payloads in parameters such as `searchName` or `tabTag` and observing if the payload is reflected and executed in the response. For example, using curl or a similar tool, you can send a POST request with a payload designed to trigger an alert dialog via XSS. A sample curl command might be: curl -X POST 'http://<target>/manage/app/resource/index' -d 'searchName=X" tabindex="1" autOfOCus ONfocUs=alert("zast-xss")//' -H 'Content-Type: application/x-www-form-urlencoded' If the response contains the injected script and it executes in a browser, the vulnerability is present. Monitoring web server logs for suspicious requests with script-like payloads in these parameters can also help detect exploitation attempts. [2]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include avoiding use of the vulnerable CacheCloud version (up to 3.2.0) and considering replacing it with an alternative product, as no official patch or response has been provided. Additionally, you can implement web application firewall (WAF) rules to block or sanitize requests containing suspicious script payloads targeting the `/manage/app/resource/index` endpoint. Educate users to avoid clicking on suspicious links that might exploit this XSS vulnerability. Ultimately, applying proper output encoding or input sanitization in the application code for parameters like `searchName` and `tabTag` is required to fully fix the issue, but since no fix is available yet, these steps serve as immediate mitigations. [3]

Useful 0 Not Useful 0