[
https://issues.apache.org/jira/browse/SOLR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945981#comment-14945981
]
Shawn Heisey commented on SOLR-3419:
------------------------------------
My boss asked me about cross-site vulnerabilities in Solr today. I remembered
reading something about some vulnerabilities, so I went looking and found this.
This issue is particularly old and the code in 5.x is likely very different.
Is this still a problem?
> XSS vulnerability in the json.wrf parameter
> -------------------------------------------
>
> Key: SOLR-3419
> URL: https://issues.apache.org/jira/browse/SOLR-3419
> Project: Solr
> Issue Type: Bug
> Components: Response Writers
> Affects Versions: 3.5
> Reporter: Prafulla Kiran
> Priority: Minor
> Attachments: SOLR-3419-escape.patch
>
>
> There's no filtering of the wrapper function name passed to the solr search
> service
> If the name of the wrapper function passed to the solr query service is the
> following string -
> %3C!doctype%20html%3E%3Chtml%3E%3Cbody%3E%3Cimg%20src=%22x%22%20onerror=%22alert%281%29%22%3E%3C/body%3E%3C/html%3E
> solr passes the string back as-is which results in an XSS attack in browsers
> like IE-7 which perform mime-sniffing. In any case, the callback function in
> a jsonp response should always be sanitized -
> http://stackoverflow.com/questions/2777021/do-i-need-to-sanitize-the-callback-parameter-from-a-jsonp-call
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
