You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/05/17 16:07:00 UTC
[jira] [Commented] (AMQ-7209) [STOMP] SecurityException stack trace
should no be in error frames
[ https://issues.apache.org/jira/browse/AMQ-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842293#comment-16842293 ]
ASF subversion and git services commented on AMQ-7209:
------------------------------------------------------
Commit 4129c1f6592616ad8731e29c95092634699f96be in activemq's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4129c1f ]
AMQ-7209 suppress stack trace in stomp error frame for SecurityExceptions to avoid any implementation detail leakage, fix and test
> [STOMP] SecurityException stack trace should no be in error frames
> ------------------------------------------------------------------
>
> Key: AMQ-7209
> URL: https://issues.apache.org/jira/browse/AMQ-7209
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> The stack trace of all exceptions is returned in the body of error frames. For security exceptions this can leak some information about the implementation and configured plugins which is not sensible.
> the stack trace should not be present for any SecurityException, just the exception message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)