qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7141) [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded
Date Mon, 16 Jan 2017 10:48:27 GMT

    [ https://issues.apache.org/jira/browse/QPID-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823763#comment-15823763

Keith Wall commented on QPID-7141:

We said that the scope of the work would be to entity encode the names/descriptions etc when
generating the HTML.  Some ConfiguredObjects have HTML markup in their descriptions.  The
HTML markup should be removed.  In the long term, formatting will be reintroduced using a
different form (possibly markdown), but this is beyond the scope of this work.

> [Java Broker] Make sure all data in the ApiDocs are correctly escaped/encoded
> -----------------------------------------------------------------------------
>                 Key: QPID-7141
>                 URL: https://issues.apache.org/jira/browse/QPID-7141
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>            Priority: Minor
>             Fix For: qpid-java-7.0
> The content of the /apidocs html page is derived from the broker which is not aware of
html semantics.
> We have to make sure the strings coming from the broker are correctly encoded before
putting them in the HTML DOM.
> OWASP has some information about correct escaping/encoding for different scenarios: https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message