|
Hi !
I edited the issue description. Do you need other samples ? Nicolas. Hi Nicolas,
Sorry not to reply until now. Thanks for the reproduction steps. I am fixing the bug now. It will be released with the next version of JIRA. Chris. This was a pretty weird bug.
The problem probably has a very minimal impact since it is only known to be reproducible with a special class of invalid XML inputs. More technical details follow: We parse the input with a SAX parser which doesn't seem to mind the presence of illegal characters like "<" in an attribute value. In the case where the Jelly tag chooses to render an error message as XML output (several tags do) and the original input cannot be parsed by the (electric xml) DOM parser (which we used to pretty print the results), then the code fell into a clause which did not properly escape the input XML when it was quoted back. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
I've been assigned to fix this problem but I'm having trouble reproducing it.
I have tried on the latest version of JIRA and made various kinds of Jelly errors occur but have been unable to see unescaped script contents in the error message.
Can you please provide some sample code that produces the problem you describe?
Also please confirm the version you are reporting this issue against. Is it happening on JIRA 3.12.2?
Regards,
Chris.