You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/09/25 00:58:33 UTC
[jira] Updated: (TAP5-1004) X-Tapestry-ErrorMessage may lead to
HTTP Response Splitting
[ https://issues.apache.org/jira/browse/TAP5-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1004:
---------------------------------------
Priority: Minor (was: Major)
Where this fix will help is when the message contains unescaped HTML characters. Those will be converted to %xx values, which helps. We then unencode them on the client side, and escapeHTML() before writing the error or debug message. Such messages now appear correctly to the user.
> X-Tapestry-ErrorMessage may lead to HTTP Response Splitting
> -----------------------------------------------------------
>
> Key: TAP5-1004
> URL: https://issues.apache.org/jira/browse/TAP5-1004
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Paul Rehrl
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> The DefaultRequestExceptionHandler sets the X-Tapestry-ErrorMessage header but fails to sanitize or encode the error message. This enables an attacker to inject malicious HTTP headers or to provide a 2nd HTTP response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.