You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2009/09/04 20:53:12 UTC
[jira] Updated: (AMQ-1272) Stomp protocol does not correctly check
authentication (security hole)
[ https://issues.apache.org/activemq/browse/AMQ-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-1272:
----------------------------
Fix Version/s: (was: 4.1.3)
5.4.0
> Stomp protocol does not correctly check authentication (security hole)
> ----------------------------------------------------------------------
>
> Key: AMQ-1272
> URL: https://issues.apache.org/activemq/browse/AMQ-1272
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Environment: 4.2-SNAPSHOT
> Reporter: Tom Samplonius
> Fix For: 5.4.0
>
> Attachments: AMQ1272-stomp-auth-v412.patch, stomp-auth.patch, stomp.diff
>
>
> ActiveMQ does not correctly validate the username and password of Stomp clients. A security exception is generated, but ignored, leaving the client connected, and with full and unrestricted access to ActiveMQ.
> Further description, and a partial patch:
> http://www.nabble.com/Getting-Stomp-support-to-a-usable-state...-tf3858629s2354.html#a11060452
> BTW, while the patch in the above post, is crude, however, leaving unauthenticated users connected with full-access makes ActiveMQ and Stomp pretty unusable. So please apply the path, rather than do nothing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.