Blocking the sendbulkemail URL caused Jira to shutdown?

Priya Ayyadevara

Hi,

 

We have recently worked on blocking the sendBulkEmail as per the latest security advisory.The change itself was fine but the application shutdown like after an  hr.

Is this expected? We are not sure what triggered this .

2019-07-25 18:23:29,545 JIRA Warmer Thread:thread-1 INFO      [c.a.jira.i18n.I18nWarmer] Initialised i18n cache in 8192 (this seems to be the last line in the log after the startup – note the gap in the time with the line below)

2019-07-25 19:51:25,867 localhost-startStop-2 INFO      [c.a.jira.startup.DefaultJiraLauncher] Stopping launchers (note sure what these lines mean – looks like a shutdown process – not sure how it got triggered)

 I can't say this might be random as the same thing happened in 4 different environments

Andy Heinzer

Hi Priya,

Blocking that specific endpoint should not cause Jira to shutdown.  The expected side-effect of blocking that endpoint is that Jira Admins won't be able to use Jira to send email in bulk to other users in Jira.

I can't think of anything in Jira that would cause that resource being restricted to cause a shutdown of Jira itself.  The log snippet you shared does appear to be that Jira is shutting down, but doesn't tell us how or why that is happening.   I would suggest creating a support case with our Jira Server support team.  You can do this by going to https://support.atlassian.com/contact/ selecting Technical issues or bugs, Jira, Server, and then entering your SEN.  I suspect that a support zip will likely be requested from your environment to try to determine the cause of the shutdown here.

It might also help to take a look at Determining whether your Jira instance has been compromised by CVE-2019-11581.  It has some other details you can investigate in your own system to see if perhaps Jira has be exploited by this vulnerability before the mitigation steps were applied.

Regards,

Andy