Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 3 Feb 2016 14:59:39 +0000 (UTC)
From: "Samir Ahmic (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12931485.1452870283000.289096.1454511579802@Atlassian.JIRA>
In-Reply-To: <JIRA.12931485.1452870283000@Atlassian.JIRA>
References: <JIRA.12931485.1452870283000@Atlassian.JIRA>
 <JIRA.12931485.1452870283181@arcas>
Subject: [jira] [Commented] (HBASE-15122) Servlets generate
 XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER findbugs warnings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-15122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130521#comment-15130521 ] 

Samir Ahmic commented on HBASE-15122:
-------------------------------------

I have seen TestRegionMergeTransactionOnCluster failing recently.  

> Servlets generate XSS_REQUEST_PARAMETER_TO_SERVLET_WRITER findbugs warnings
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-15122
>                 URL: https://issues.apache.org/jira/browse/HBASE-15122
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Critical
>         Attachments: HBASE-15122-v0-master, HBASE-15122.patch, HBASE-15122_v1.patch, HBASE-15122_v2.patch
>
>
> In our JMXJsonServlet we are doing this:
>         jsonpcb = request.getParameter(CALLBACK_PARAM);
>         if (jsonpcb != null) {
>           response.setContentType("application/javascript; charset=utf8");
>           writer.write(jsonpcb + "(");
> ... 
> Findbugs complains rightly. There are other instances in our servlets and then there are the pages generated by jamon excluded from findbugs checking (and findbugs volunteers that it is dumb in this regard finding only the most egregious of violations).
> We have no sanitizing tooling in hbase that I know of (correct me if I am wrong). I started to pull on this thread and it runs deep. Our Jamon templating (last updated in 2013 and before that, in 2011) engine doesn't seem to have sanitizing means either and there seems to be outstanding XSS complaint against jamon that goes unaddressed.
> Could pull in something like https://www.owasp.org/index.php/OWASP_Java_Encoder_Project and run all emissions via it or get a templating engine that has sanitizing built in. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)