activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Samplonius (JIRA)" <>
Subject [jira] Commented: (AMQ-1272) Stomp protocol does not correctly check authentication (security hole)
Date Sun, 24 Jun 2007 05:59:34 GMT


Tom Samplonius commented on AMQ-1272:

I have re-tested the patch.  I applied the patch (more or less) to activemq-5.0-20070621

The behaviour is a bit strange.  A Stomp producer simply blocks (I'm using Net::Stomp).  A
Stomp consumer does too.  Very odd.  At least unauthenticated Stomp clients can't steal messages.

I'm going to try to attach my patch (context diff).

> Stomp protocol does not correctly check authentication (security hole)
> ----------------------------------------------------------------------
>                 Key: AMQ-1272
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: 4.2-SNAPSHOT
>            Reporter: Tom Samplonius
>            Priority: Blocker
>             Fix For: 4.1.2, 5.0.0
> 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:

> 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.

View raw message