This vuln actually affects the H2 database that ships with Jira. Affected versions of Insight allow it to be exploited, but it's best to assume that there could be other attack vectors as well. My recommendation would be to follow the Mitigation steps in the announcement even if you don't intend to use Insight. Of course, this means you need to use a production grade database and migrate off of H2. H2 serves no useful purpose if you are using a supported database, so you should remove it.
![Dave Theodore [Coyote Creek Consulting]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/557058:a1f94001-e8c1-4ab0-95d3-01a204687231/254ecf19-a9ab-40df-9b8a-51a3251ea418/128 "Dave Theodore [Coyote Creek Consulting]"){kind=avatar}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.