Cross-Site Scripting vulnerability in Websense Data Security block page
It was discovered that the Websense Data Security block page processes user-controllable data insecurely, rendering the block page is vulnerable to Cross-Site Scripting. Cross-Site Scripting allows an attacker to perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
This issue was discovered on Websense Triton v7.8.3 and Websense appliance modules V-Series v7.7. Other versions may be affected as well.
This issue is resolved in TRITON APX Version 8.0. More information about the fixed can be found at the following location:
Websense Data Security Suite contains three modules - Data Security Gateway, Data Discover, and Data Endpoint - that can help manage the risk of losing your data to malicious users or accidental misuse.
When Data Security DLP policies block a website, a block page is displayed in the client's browser. The message presented to the user is send back to the server using Base64 encoding. This message contains user related information such as the IP address of the client. The message is not properly encoded when used in the block page. Consequently, the block page is vulnerable to Cross-Site Scripting.
In order to exploit this vulnerability a valid ws-session is required. The payload has to be Base64 encoded, submitted to the block page via the ws-encdata URL parameter. For example, the following parameters can be submitted to the block page.
The above parameters must then be encoded with Base64 and appended to the following URL:
An attacker must trick victims into opening the attacker's specially crafted link. This is for example possible by sending a victim a link in an email or instant message. Once a victim opens the specially crafted link, arbitrary client-side scripting code will be executed in the victim's browser. The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session tokens or login credentials, performing arbitrary actions on their behalf, logging their keystrokes.
Thanks for reading.
Shipping secure products?
When building software, security bugs are introduced. Don’t wait until the last minute to find them. A security source code review or penetration test (pentest) is a highly effective method to evaluate the security quality of your applications. When building software, ensure to verify security early and often (Agile Security Testing) to ship quality, secure by design products.