You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/01/06 15:49:35 UTC
[jira] [Commented] (SLING-4177) Sightly: StyleString context
doesn't properly escape
[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266183#comment-14266183 ]
ASF GitHub Bot commented on SLING-4177:
---------------------------------------
Github user vladbailescu closed the pull request at:
https://github.com/apache/sling/pull/52
> Sightly: StyleString context doesn't properly escape
> ----------------------------------------------------
>
> Key: SLING-4177
> URL: https://issues.apache.org/jira/browse/SLING-4177
> Project: Sling
> Issue Type: Bug
> Components: Extensions, Scripting
> Reporter: Vlad Bailescu
> Assignee: Felix Meschberger
> Priority: Minor
> Labels: Sightly
> Fix For: XSS Protection API 1.0.0, Scripting Sightly Engine 1.0.0
>
>
> The {{context='styleString'}} expression option seems to escape strings the same way as {{context='scriptString'}}, but this breaks the string, making that context unusable. CSS strings are to be escaped {{\HH}} and not {{\xHH}} like in JS:
> https://developer.mozilla.org/en-US/docs/Web/CSS/string
> Consider following example:
> {code:html}
> <style>
> .ft:after { content: "${'\'' @ context='styleString'}"; }
> .in:after { content: "${'\"' @ context='styleString'}"; }
> </style>
> {code}
> Which currently gets incorrectly rendered as follows:
> {code:html}
> <style>
> .ft:after { content: "\x27"; }
> .in:after { content: "\x22"; }
> </style>
> {code}
> Following output would have been expected:
> {code:html}
> <style>
> .ft:after { content: "\27"; }
> .in:after { content: "\22"; }
> </style>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)