You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/03/03 14:50:00 UTC

[jira] [Resolved] (AMQ-7434) Enable Jolokia CORS strict-checking by default

     [ https://issues.apache.org/jira/browse/AMQ-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved AMQ-7434.
---------------------------------------
    Resolution: Fixed

> Enable Jolokia CORS strict-checking by default
> ----------------------------------------------
>
>                 Key: AMQ-7434
>                 URL: https://issues.apache.org/jira/browse/AMQ-7434
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Web Console
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: 5.16.0, 5.15.12
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> By default, we should enable Jolokia CORS strict-checking by default. Otherwise the web console is potentially vulnerable to a CSRF style attack, as Jolokia allows all origins by default.
> This change has a minor backwards compatibliity implication - a REST client must specify (some) Origin header in the request - and also calling from "localhost" in the browser won't work.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)